Occasional stream corruption

[MikeQ]

Hi all,

I have a server process using netty.  Part of the netty implementation is a
simple request/response handler. Clients connect to the server and make
synchronous request/response calls.

Occasionally I get a stream corruption on the client as if the server has
sent some duff data or the packets got misordered.  It only happens
sometimes, for example I can start the client up and the error occurs during
the startup, then if I stop and start the client again it works fine.  I'm
inclined to believe this is some threading issue in my netty handler code.

My first thought is the order the packets I am sending from the server is
getting out of order before they are physically sent.  If I only have one
thread writing to a channel is the order of the .write() going to be the
order they are put on the wire and received by the other end?  This would
explain my issue.

Any help appreciated.

Cheers.
-- 
View this message in context: http://n2.nabble.com/Occasional-stream-corruption-tp3993030p3993030.html
Sent from the Netty User Group mailing list archive at Nabble.com.