"Kevin.Conner(a)jboss.com" wrote : "tfennelly" wrote : Sorry, typo. Should have been "When you saying 'two separate parameters', do you mean allow it to be configured centrally in the jbossesb-properties.xml and then override it in the JNDI config?" | I hadn't meant that as I had assumed that the default behaviour would be as now, so if the user does not specify it then it works the same. OK, we're fine on that then because the default behavior is as is now. "Kevin.Conner(a)jboss.com" wrote : I was thinking more from the configuration aspect, supporting both an XA and a non-XA version of this parameter within JNDI. | | If we choose to do this then the user can set it up once in the jms-provider and the same configuration/pool can be shared between all the associated listeners, whether transactional or not. | | If there is only a single JNDI parameter then the user may get into problems if they mix transactional/non-transactional listeners and would have to be aware of the issues. Would they get into "problems", or would they simply be eating more connections off the provider than they needed to in the non-XA? It's just that I think this would complicate and already convoluted implementation a little bit more. Maybe we could save this for the "improved" version of this class, whenever that happens :) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4231339#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...