[jboss-jira] [JBoss JIRA] Closed: (JBMESSAGING-1417) Provide thread pools with ordered executors for session threads

[Clebert Suconic (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBMESSAGING-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Clebert Suconic closed JBMESSAGING-1417.
----------------------------------------

    Fix Version/s: 1.4.1.GA
       Resolution: Done


> Provide thread pools with ordered executors for session threads
> ---------------------------------------------------------------
>
>                 Key: JBMESSAGING-1417
>                 URL: https://jira.jboss.org/jira/browse/JBMESSAGING-1417
>             Project: JBoss Messaging
>          Issue Type: Feature Request
>            Reporter: Tim Fox
>            Assignee: Howard Gao
>             Fix For: 1.4.1.GA, 1.4.2.GA,  1.4.0.SP3.CP04
>
>
> Currently, each session on both server and client side maintains its own thread.
> If a very large number of sessions are created this can results in a large number of threads created which may be a problem on some  operating systems.
> We can fairly easily remedy this by using a static OrderedExecutorFactory initialised with a cached thread pool and JBMThreadFactory for both client and server session threads.
> This is the way it is currently done in JBM 2.0

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira