Hi Claus,
Yes, you are right about exhausted.
I recognized that when got that code working as expected with redelivery.
Just in case if this could be helpful for someone other let me write down
changes I've made to above code.
1. Moved Camel's JMS component configuration to separate bean with added
cache level (CACHE_CONSUMER):
<bean id="camelJmsComponent"
class="org.apache.camel.component.jms.JmsComponent">
<property name="configuration" ref="jmsConfig"/>
</bean>
<bean id="jmsConfig"
class="org.apache.camel.component.jms.JmsConfiguration">
<property name="connectionFactory" ref="jmsConnectionFactory" />
<property name="transacted" value="true" />
<property name="transactionManager" ref="jmsTransactionManager" />
<property name="cacheLevelName" value="CACHE_CONSUMER" />
</bean>
2. Added maxConnections property to the JMS pooled connection factory (with
value 8).
Now the code works excellent with redelivery.
Thanks.
--Victor
--
View this message in context:
http://camel.465427.n5.nabble.com/JMS-transaction-behavior-inside-of-route-tp5730513p5731608.html
Sent from the Camel - Users mailing list archive at Nabble.com.
