The client is reporting an error that implies the server either closed the connection or timed out. As I can see the packet being written in the logging filter well before the timeout expires coupled with the closed log message I have to assume it's the server closing the connection. I can't really see what's going on in the internals of the client as it's 3rd party so all I have are the error codes.
On 3 April 2013 17:34, Emmanuel Lécharny <[email protected]> wrote: > Le 4/3/13 6:02 PM, Jennifer Cumming a écrit : > > Added and nothing. exceptionCaught is not getting called. Even tried > > putting a breakpoint in and debugging and it's not getting hit. > > Ok, at least, that says it's not an exception... > > Isn't it possible that your client closes the connection ? > > Btw, you should set the TcpNoDelay to true, unless you are sending a lot > of data. > > -- > Regards, > Cordialement, > Emmanuel Lécharny > www.iktek.com > >
