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

[Christian Migowski]

Hi Trustin,

On Tue, Jan 18, 2011 at 9:58 AM, ljohnston <johnstlr at yahoo.co.uk> wrote:
...
> If you're using a fixed sized thread pool you need to tell netty how many
> threads are in the pool. This goes for both NioServerSocketChannelFactory
> and NioClientSocketChannelFactory. Both have an alternative constructor
> which takes a third argument of workerCount.

This should be noted in the Javadoc of the channel factory. Recently
people here on the list complained about Netty not being able to
handle more connections than they had threads in their fixed size
thread pool, assuming Netty is one thread per connection and so on,
all which is caused by Netty assuming too many workers than actually
exist, no?


> If you don't do this Netty assumes there are (2 * number of available
> processors) threads available. This might be why you're seeing threads
> getting in each other's way.
>
> See if that solves your problem.
>
> Cheers
> Lee
> --
> 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-tp5933385p5934892.html
> Sent from the Netty User Group mailing list archive at Nabble.com.
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users
>