[Jboss-dev-forums] [Design of the JBoss EJB Container] - MDB pooling

[<ad...@jb...>]

This is the discussion thread for:
http://jira.jboss.com/jira/browse/JBAS-2047

The ServerSessionPool implementation is entirely configurable/replaceable, see jms-ds.xml

I would be interested in an implementation that allows a thread single pool for all mdbs.

Sub pools based on message parameters or the subscription are an enhancement to this.
Infact, the current implementation can be viewed as one sub-pool per subscription.

However, it needs to be understood what happens at exhaustion of the pool. 
i.e. How is it decided which subscriptions/mdb gets the next thread. 
I would think the default implementation of such a scheduling policy should be based on message priority.

There are also issues relating to "singleton" and clean mdb shutdown that are currently implemented based
on the thread pooling semantics.

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

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