Hi James,
Anurag tried to use the JMSComponent with the spring
SingleConnectionFactory. This should ensure that only one connection is
used.
So I would not expect that such an error should happen. In any case I
fear that this problem could also happen with other jms providers that
do not have a special module in Camel.
Greetings
Christian
James Strachan schrieb:
2008/12/10 Christian Schneider <[EMAIL PROTECTED]>:
Hi Claus,
if it worked with the ActiveMQComponent but not with the JMSComponent then
do we have a bug in the JMSComponent?
No - its that using the JMSComponent with a 'naked'
ActiveMQConnectionFactory does absolutely no pooling whatsoever -
causing a new connection/session/producer/consumer to be created for
every single message being sent/received which is bad...
see
http://activemq.apache.org/jmstemplate-gotchas.html
So I'd recommend never using JMSComponent if you are using ActiveMQ;
we've specifically made the ActiveMQComponent so it does things right
out of the box so you don't mess up :)
--
Christian Schneider
---
http://www.liquid-reality.de
