<div>If there is no open connection assigned to a worker thread, the thread will be returned to the thread pool after a while. Sometimes, when a worker thread is being returned to the pool and another thread is being pulled again because of a new connection, the number of the threads borrowed from the pool will exceed the maximum number of worker threads. However, this happens only briefly, and that's why you have to use newCachedThreadPool(). If you specified the number of worker threads as 4 and specified a fixed thread pool with 4 threads, it will be locked up because sometimes Netty will need 5 threads, although it never means I/O will take place in more than 4 threads.<br></div>
<div><br>-- <br>Trustin Lee<br>Sent with <a href="http://www.sparrowmailapp.com/?sig">Sparrow</a><br></div>
<p style="color: #A0A0A8;">On Thursday, October 20, 2011 at 7:08 AM, Norman Maurer wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div>Maybe I don't remember correctly. I will have a deeper look again.<br><br>Thanks,<br>Norman<br><br>Am Donnerstag, 20. Oktober 2011 schrieb Bill Burke <<a href="mailto:bburke@redhat.com">bburke@redhat.com</a>>:<br>
> I don't think you are right. I've been looking at the NIO code deeply<br>> the past few days and the set of workers is a fixed array[]. The accept<br>> thread does a register on a round-robin-picked worker. If the worker is<br>
> already started, then the accepted socket is added to the worker's<br>> selector. If the worker isn't started, then it gets added to the worker<br>> Executor.<br>><br>> OiO is different though and *does* do a thread-per-connection.<br>
><br>> On 10/20/11 9:36 AM, Norman Maurer wrote:<br>>> Hi Bill,<br>>><br>>> the "max" cocurrent io threads are limited thats right. But it may<br>>> spin a new thread for some reasons before one can get destroyed or put<br>
>> back..<br>>><br>>> See also:<br>>> <a href="http://netty-forums-and-mailing-lists.685743.n2.nabble.com/Help-with-limiting-number-of-possible-channels-td6464491.html#none">http://netty-forums-and-mailing-lists.685743.n2.nabble.com/Help-with-limiting-number-of-possible-channels-td6464491.html#none</a><br>
>><br>>> Bye,<br>>> Norman<br>>><br>>> Ps: I think its also somewhere explained in the javadocs but I don't<br>>> know where atm<br>>><br>>> 2011/10/20 Bill Burke<<a href="mailto:bburke@redhat.com">bburke@redhat.com</a>>:<br>
>>> Isn't the amount of workers fixed at bootstrap (at least for NIO)?<br>>>><br>>>> On 10/20/11 3:46 AM, ljohnston wrote:<br>>>>> Hi Irwin<br>>>>><br>>>>> Those threads seem to come from the Eclipse runtime. Assuming your code<br>
>>>> isn't some sort of Eclipse plugin can you run it outside of eclipse and see<br>>>>> if the behaviour changes? Otherwise it looks like something is spawning<br>>>>> Eclipse jobs and Eclipse isn't releasing the threads.<br>
>>>><br>>>>> Cheers<br>>>>> Lee<br>>>>><br>>>>><br>>>>> --<br>>>>> View this message in context: <a href="http://netty-forums-and-mailing-lists.685743.n2.nabble.com/Threads-New-Connections-tp6859861p6911955.html">http://netty-forums-and-mailing-lists.685743.n2.nabble.com/Threads-New-Connections-tp6859861p6911955.html</a><br>
>>>> Sent from the Netty User Group mailing list archive at <a href="http://Nabble.com">Nabble.com</a>.<br>>>>> _______________________________________________<br>>>>> netty-users mailing list<br>>>>> <a href="mailto:netty-users@lists.jboss.org">netty-users@lists.jboss.org</a><br>
>>>> <a href="https://lists.jboss.org/mailman/listinfo/netty-users">https://lists.jboss.org/mailman/listinfo/netty-users</a><br>>>><br>>>> --<br>>>> Bill Burke<br>>>> JBoss, a division of Red Hat<br>
>>> <a href="http://bill.burkecentral.com">http://bill.burkecentral.com</a><br>>>> _______________________________________________<br>>>> netty-users mailing list<br>>>> <a href="mailto:netty-users@lists.jboss.org">netty-users@lists.jboss.org</a><br>
>>> <a href="https://lists.jboss.org/mailman/listinfo/netty-users">https://lists.jboss.org/mailman/listinfo/netty-users</a><br>>>><br>>> _______________________________________________<br>>> netty-users mailing list<br>
>> <a href="mailto:netty-users@lists.jboss.org">netty-users@lists.jboss.org</a><br>>> <a href="https://lists.jboss.org/mailman/listinfo/netty-users">https://lists.jboss.org/mailman/listinfo/netty-users</a><br>
><br>> --<br>> Bill Burke<br>> JBoss, a division of Red Hat<br>> <a href="http://bill.burkecentral.com">http://bill.burkecentral.com</a><br>> _______________________________________________<br>> netty-users mailing list<br>
> <a href="mailto:netty-users@lists.jboss.org">netty-users@lists.jboss.org</a><br>> <a href="https://lists.jboss.org/mailman/listinfo/netty-users">https://lists.jboss.org/mailman/listinfo/netty-users</a><br>>
</div><div>_______________________________________________<br>netty-users mailing list<br><a href="mailto:netty-users@lists.jboss.org">netty-users@lists.jboss.org</a><br><a href="https://lists.jboss.org/mailman/listinfo/netty-users">https://lists.jboss.org/mailman/listinfo/netty-users</a><br></div></div></span>
</blockquote>
<div>
<br>
</div>