Structured message reading problem in Netty.

[Frederic Bregier]

Hi Manish,

DISONNECTED and UNBOUND obviously mean that the channel is closed.
Either the server or the client can be the root of the disconnection.

>From your handler, it does not seemed that it is the root cause.

Could it be your client that try to send one packet and then to disconnect,
or another scenrario, client connects, then sends all they packet and
doesn't wait
anything from the server to disconnect ?

For instance:
- client try to connect
- server creates all necessary handlers
- client as soon as it is connect send the packets
- server starts to receive one packet
- client don't wait for anything from the server after sending all its
packet
  (from its point of view) and close the connection.
- server has only the time to consume one packet and then get the
disconnection
  so that it cannot goes to the next messages... (I think disconnection is
  prioritary to any other messages) 

If so, perhaps you should have to send something like a "end of
transmission" from
the server to the client, the client will wait for this ackonwledge to close
the connection... ?

HTH,
Frederic


-----
Hardware/Software Architect
-- 
View this message in context: http://n2.nabble.com/Structured-message-reading-problem-in-Netty.-tp2682454p2752469.html
Sent from the Netty User Group mailing list archive at Nabble.com.