My recommendation is to start simple and add complexity as-needed. What does a pooled connection add to the solution? If nothing, remove it. In general, pooled connections are useful for two key concerns:
- Processing flows which do not keep connections for long periods (e.g. open connection / process 1 msg / close connection) - Clients with a fair-to-large number of consumers to various destinations; pooling here helps to share resources across consumers (e.g. 100 consumers on 10 connections) -- at the cost of reduced throughput. Durable subscriptions do not play well with pooled connections. In that case, use individual connections. Using a pool with max connections set to 1 may work to reuse the connection across mutiple consumers - I haven't tried it. In the posted config, remove the pooled connection factory. The multiple client IDs are fatal. -- View this message in context: http://activemq.2283324.n4.nabble.com/ActiveMQ-pooled-Connection-Factory-for-multiple-durable-subscribers-tp4684735p4684762.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
