Randomly getting unexpected bytes in the ChannelBuffer from test client with valid data

tnine todd at spidertracks.com
Tue Jan 18 17:03:28 EST 2011


Hey guys,
  Thanks for the help guys.  Unfortunately that doesn't seem to fix my
issue.  My client is using an unbounded Executor thread pool created with a
call  toExecutors.newCachedThreadPool().


If I log the number of bytes in my decoder, I receive 71 as expected for the
real message.  I then immediately receive another call to my decoder with 0
bytes. The call to "buffer.readableBytes()" always returns 0.  Any ideas why
my decoder is still getting invoked if no bytes are left on the channel? 
I've updated my server and the gist with your suggestions, but it hasn't
resolved my issue.


https://gist.github.com/88dd0f8b5a42c2aa736d
-- 
View this message in context: http://netty-forums-and-mailing-lists.685743.n2.nabble.com/Randomly-getting-unexpected-bytes-in-the-ChannelBuffer-from-test-client-with-valid-data-tp5933385p5937408.html
Sent from the Netty User Group mailing list archive at Nabble.com.


More information about the netty-users mailing list