Randomly getting unexpected bytes in the ChannelBuffer from test client with valid data
tnine
todd at spidertracks.com
Mon Jan 17 18:39:22 EST 2011
Just an update. This issue seems to be related to using the following with
the client
ExecutorService workers = Executors.newFixedThreadPool(5);
With a max thread pool defined, the data I receive is not always what I send
via the data channel. If I use this
ExecutorService workers = Executors.newCachedThreadPool();
I never have this issue. I've logged all the binary I receive, and it
appears to be jumbled. I.E. it looks like 2 threads are writing to the same
channel, so the bytes are not consecutively written by each thread. Am I
doing something wrong in my client? I only experience this when using a
different Executor pool per thread. I.E I partition my input file to be
read over 4 threads. Each one of the reader threads has a client connection
pool of 5 threads.
--
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-tp5933385p5933927.html
Sent from the Netty User Group mailing list archive at Nabble.com.
More information about the netty-users
mailing list