I am using the bitronix.tm.resource.jms.PoolingConnectionFactory to manage JMS connections for a Spring\ActiveMQ application.Because of the design of the application, I have 6 separate org.springframework.jms.listener.DefaultMessageListenerContainer classes that I initially wanted to associate with one PoolingConnectionFactory. However, the maxPoolSize limit of 5 means that the PoolingConnectionFactory cannot handle all the DMLC instances.
With the assumption that I cannot change the number of DMLC's, should I be using multiple PoolingConnectionFactorys to handle the DMLCs? Will using multiple PoolingconnectionFactorys cause any other problems?
In the longer term, the maxPoolSize limit of 5 seems quite low. Would it be possible to extend this, or would there be some performance\design trade-off to do this?