Thank you very much. Once I did the osgi:update it worked as expected.
While I thought I had the default activemq-broker.xml, it was not. The
following text was added to the default activemq-broker.xml.
<deadLetterStrategy>
<individualDeadLetterStrategy queuePrefix="DLQ."
useQueueForQueueMessages="true" />
</deadLetterStrategy>
+ Which I grabbed from here:
http://activemq.apache.org/message-redelivery-and-dlq-handling.html
++++++++++++++++++++++++++++++++++++++++++++++++++++++
To other readers doing something similar, I also updated my Redelivery
Policy to be specific about jms behaviour
(http://activemq.apache.org/redelivery-policy.html), as this configuration
has to be done client side:
<bean id="jmsXaConnectionFactory"
class="org.apache.activemq.ActiveMQXAConnectionFactory">
<property name="brokerURL" value="tcp://localhost:61616" />
<property name="redeliveryPolicy">
<bean class="org.apache.activemq.RedeliveryPolicy">
<property name="initialRedeliveryDelay" value="1000"/>
<property name="backOffMultiplier" value="5"/>
<property name="useExponentialBackOff" value="true"/>
<property name="maximumRedeliveries" value="6"/>
</bean>
</property>
</bean>
+++++
On an unrelated issue, I made a mistake with one of my above beans, when I
forgot the sessionTransacted property. It should read.
<bean id="jmsTemplate" class="org.springframework.jms.core.JmsTemplate">
<property name="connectionFactory" ref="atomikosConnectionFactory" />
<property name="sessionTransacted" value="true" />
</bean>
--
View this message in context:
http://servicemix.396122.n5.nabble.com/JMS-and-Database-interactions-under-the-same-transactional-context-tp4762819p4940935.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
