|
Reading the docs, I do not think that parm would help right now. However, if it did, you would have to change it in the other direction. In other words, change it from 120 to something like 30. The setting is how many minutes for the system to wait before sending out a KeepAlive ping. So you would want a shorter delay in case you have a proxy server or router which would close the connection after some period of inactivity. This setting will keep the connection alive during inactivity. The reason I do not think it will help right now, is that I do not think JT400 turns on the KeepAlive feature by default in its connections. Mark wdsci-l-bounces@xxxxxxxxxxxx wrote on 09/13/2004 09:54:01 AM: > Mark, > > We changed the TCP keep alive value to 540 some time ago at an attempt to > keep these jobs alive for the day. So yeah, not a factor. I'll check out the > JT400 forum. > > Best regards, > > Gregg Willow > Programmer/Analyst > Minnesota Counties Information Systems > 413 SE 7th Avenue > Grand Rapids, MN 55744 > 218-326-0381 ext: 17 > gregg.willow@xxxxxxxxxxxxxx _____________________________________________________________________________ Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs. _____________________________________________________________________________
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.