Thanks for your reply. I was trying out the 'consumerType' option, as well as 'serverSessionFactory'. It does not bring me any further, I receive:
"javax.jms.JMSException: Session pool provided an invalid session type: class org.apache.activemq.pool.PooledSession" We have also debuged the camel/activemq and got a strong impression that the issue in question is actually a bug on the Camel side. Jason Anderson-3 wrote: > > not sure if this is helpful but you can switch the container > implementation on the component > > > <bean id="jms" class="org.apache.camel.component.jms.JmsComponent"> > <property name="consumerType" value="ServerSessionPool"/> > <!-- other properties here --> > </bean> > > -- View this message in context: http://www.nabble.com/DefaultMessageListenerContainer%2C-pooling-problem-tf4772431s22882.html#a13655603 Sent from the Camel - Users mailing list archive at Nabble.com.
