Paul Roy,I can't see what this has to do with the error he's describing? I wonder if you're confusing two different things?
With Java applications (and only with Java... I suspect this is a bug somewhere deep in the JVM) I've seen issues where TCP connections will sporadically disconnect, and setting the keep-alive value (i.e. the CHGTCPA option you mention) to a small value works around this bug.
But that's not at all related to what Paul Kenosky is describing. He's saying that his session never ends or times out -- so pretty much the opposite. It seems unlikely that this keep-alive value would solve that, unless there's something that I'm not thinking of?
-SK On 1/8/2016 5:32 AM, Paul Roy wrote:
Hi,
this looks to me like a communication error... either the remote did
not receive your data or you did not receive the response...
I had the same kind of issues (not with HTTPAPI but a Java pgm) that
was solved by shortening the tcp keep alive value (if i remember
correctly, the time that the TCP stack waits before closing the socket
. if there is no traffic)
the default value is 2 hours and can be changed with CHGTCPA
TCPKEEPALV(1) to set 1 minute... you can also change the option of the
socket wit set_sock_options()... but I do not know if te option is
available in HTTPAPI
then you should add some logic in your program to try again...
----------------------------------------------------------------------- This is the FTPAPI mailing list. To unsubscribe, please go to: http://www.scottklement.com/mailman/listinfo/ftpapi -----------------------------------------------------------------------