The behaviour is caused by spring jms and is normal. The spring jms code
opens and closes the connection for every call. This is the expected
behaviour in JEE environments.
To improve the performance you need connection pooling.
Spring provides the
http://static.springsource.org/spring/docs/2.5.x/api/org/springframework/jms/connection/CachingConnectionFactory.html
for that.
You can wrap your original connection factory with it.
Alternatively you can check if MQ provides a pooling connection factory.
Christian
Am 13.04.2012 11:11, schrieb weberj:
Hi,
we found that Camel together with the JMS component over Websphere MQ is
quite slow, it takes up to a second for Camel to forward a message.
There is an old bug which might explain this behaviour:
New JMS connection being created for every message
https://issues.apache.org/jira/browse/CAMEL-604
I did a trace of MQ within Camel, and there were indeed a lot of MQOPEN
calls, so I guess the problem is still there.
Can anybody confirm this? Is the bug still there? Is there a work-around?
Any chance of this bug getting fixed?
Thanks,
Juergen
--
View this message in context:
http://camel.465427.n5.nabble.com/New-JMS-connection-being-created-for-every-message-tp5637735p5637735.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
