[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Bounding the number of threads created by the MDB container

[ovidiu.feodorov@jboss.com]

Each MDB container deployment that uses the standard JBoss JMS JCA adapter creates a pool of 15 (default number, but configurable) server sessions, and each such server session starts by default at least 2 new threads (the executors of the server side session endpoint and the client side session delegate). That is 30 JBM threads per MDB deployment.

Each MDB deployment can be tuned to reduce its number of server sessions, but a little more elegant solution would be to allow JBM to accept a thread pool for all its primitives to use. This is the spirit of http://jira.jboss.com/jira/browse/JBMESSAGING-1356.

This way, an instance administrator can put a upper bound to the total number of threads used by MDBs within an instance, regardless of an MDB individual configuration. 

Generalizing, if one wants to limit the maximum number of threads used by JBM within a VM, should be able to configure all thread-related JBM primitives to use a central thread pool.


I'll take a stab at implementing this. 

What branch should I apply my patch on?



View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4156830#4156830

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4156830