In GFv2.x and v3 we use different thread pools for different listeners.
The problem here is cyclic calling (1) -> (2) -> (1), which causes the
mentioned block.
Alexey.
On Jun 23, 2010, at 22:21 , glassfish_at_javadesktop.org wrote:
> Is this glassfish 3?
>
> I would suggest using different thread pools for the different
> listeners.
>
> We have a number of applications that are similar: lots of
> concurrent requests (>100/second) to one listener (80), each of
> those needs to make a request to another webservice at a different
> port. If you assign the same threadpool to both listeners, you can
> easily get blocked as requests to the first are waiting for a
> connection to the second, but the maximum amount in the threadpool
> is reached (all threads occupied by the first listener, nothing
> available for the second listener)
>
> We run more than 100 requests per second, with 2 threadpools of 8
> max threads each.
>
> Not sure this answers your question, but I hope it does help.
>
> - Johan
> [Message sent by forum member 'johanvos']
>
> http://forums.java.net/jive/thread.jspa?messageID=475586
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>