This is then probably an issue with the resource adapter. As far a I
understood a Java EE application is expected to close the connection
after each method call and the
pool should then handle that this still is performant.
Christian
Am 26.04.2012 11:40, schrieb weberj:
This was my original configuration that pooling was in the resource adapter
(the MQ RA has a default of 10 maxConnections).
But when Camel closes the connection this somehow seems to close the RA's
underlying connection, too.
--
View this message in context:
http://camel.465427.n5.nabble.com/New-JMS-connection-being-created-for-every-message-tp5637735p5667139.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
Talend Application Integration Division http://www.talend.com
