Threads & New Connections

[irwinbilling]

Hello,

I seem to be running into a very peculiar problem.  Using the default
ChannelFactory (Executors.newCachedThreadPool()) with a custom
ChannelPipeline, the server seems to stop serving new connections after 39
successful connections and message exchanges.

When looking at the list of running threads, it seems that for every new
connection, a new thread is started.  When the channel disconnects, the
thread stays alive (waiting at Unsafe.park).  This happens until the 40th
connection when the CHannelFactory.getPipeline() does not get called.

What could cause an issue of this sort?

Thanks!

--
View this message in context: http://netty-forums-and-mailing-lists.685743.n2.nabble.com/Threads-New-Connections-tp6859861p6859861.html
Sent from the Netty User Group mailing list archive at Nabble.com.