Yes. The control connection is what is timing out. I've seen other
clients (FileZilla etc) use a timer to send NOOPs over the control
connection periodically.
And Meeraj, yes, I think there may be a potential race condition with
NOOPs being executed whilst another command is currently pending.
On 3 Mar 2009, at 22:14, sebb wrote:
Aren't there two connections involved here - i.e. the control and data
connections?
Surely the data connection will be kept alive by the STOR command; the
NOOP is presumably only needed on the control connection?
I would question whether the F5 load balancer is working correctly if
it fails to take the data connection traffic into account. But I could
be wrong.
On 03/03/2009, Meeraj Kunnumpurath <[email protected]>
wrote:
Hi,
That is what I have done.
If I do the STOR and NOOP on two threads, isn't there a possible race
condition with the response for STOR and NOOP coming back the same
time as
they share the same socket?
Ta
Meeraj
On Tue, Mar 3, 2009 at 6:54 PM, Daniel F. Savarese
<[email protected]> wrote:
In message <[email protected]>, Rory
Winston
writ
es:
Currently, FTPClient doesnt support keepalive, but I suspect that
it
probably should. I'll raise a JIRA ticket.
There's nothing stopping the programmer fromn sending a NOOP every
t seconds over the control connection. However, if one expects
FTPClient to do it automatically, then, sure, it doesn't support it.
daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
