On 11/22/11 4:11 PM, pinus wrote:
Julien Vermillard-2 wrote:
On Tue, Nov 22, 2011 at 11:22 AM, Emmanuel Lecharny<elecha...@gmail.com>
wrote:
You should try to capture the TCP stream with wireshark or tcpdump.
Could give you a clue about what is triggering the end of TCP session.
Sorry for the three posts, nabble.com crashed on me and I tried again before
noticing that it already posted it.
I already have a wireshark dump, it tells me that my application sends the
TCP-FIN. I send a message, get an application ACK for it and send the next
message. About 60ms later I send the TCP-FIN.
I have a ProtocolEncoder and ProtocolDecoder which do log the traffic. Is
the registered logger something else?
I have logging before each session.close() message but I can not see a
message. Everything looks like I'm waiting for the application ACK. During
waiting another thread creates a sessionClosed() event. It's just a guess
but it looks like the sending of the message fails (produces an error) which
close the session. Between sending the message and the sessionClosed() are
about 60ms. The strange thing is that I can't see any error.
Even if you implement the exceptionCaught() event in your handler ?
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
