Greetings:
The only way that I can get AMQ 5.2 to properly route an invalid message to
the DLQ is if I use a Non XA connection and set sessionTransaction=true. We
would prefer to use XA if possible.
Is there a known issue with redelivery policy and XA?
Any help would be appreciated.
Could it be an error with my configuration?
<!-- XA Pooled Connection Factory -->
<bean id="jmsConnectionFactory"
class="org.jencks.pool.PooledSpringXAConnectionFactory">
<property name="connectionFactory">
<bean class="org.apache.activemq.ActiveMQXAConnectionFactory">
<property name="brokerURL"
value="failover:tcp://${jms.broker.host}:${jms.broker.port}"/>
<property name="redeliveryPolicy">
<bean class="org.apache.activemq.RedeliveryPolicy">
<property name="initialRedeliveryDelay" value="600" />
<property name="maximumRedeliveries" value="2" />
</bean>
</property>
</bean>
</property>
<property name="jtaTransactionManager" ref="transactionManager"/>
</bean>
--
View this message in context:
http://www.nabble.com/DLQ-and-XA-Connection-Factory-with-Spring-tp21751613p21751613.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
