Le 4/3/13 9:50 PM, Jennifer Cumming a écrit : > 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 Are you receiving a messageSent event ? If not, that means the message has not been sent to the client (this event is generated when the full message has been written into the socket).
> 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. At this point, you should first verify that the data exchanged between your server and the client are what you expect them to be. You can use Wireshark for that. On my side, it's rather difficult to tell you what can be wrong without seing the code... > > > 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 >> >> -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
