Hi all,
Since 5.4.2 all messages handle by the consumer remain on the queue forever,
even though they are already processed.
I'm clashing with a problem since the upgrade to 5.4.2. The previous
versions aren't affected by this problem.
The application consists of a spring based consumer which is XA transacted
with mysql through atomikos.
Have you any hint on this?
These are the conf:
consumer:
<bean id="xaFactory"
class="org.apache.activemq.ActiveMQXAConnectionFactory" >
<property name="brokerURL" value="${jms.providerUrl}" />
<property name="prefetchPolicy">
<bean class="org.apache.activemq.ActiveMQPrefetchPolicy" >
<property name="queuePrefetch" value="10"/>
</bean>
</property>
<property name="redeliveryPolicy">
<bean class="org.apache.activemq.RedeliveryPolicy">
<property name="initialRedeliveryDelay" value="1000"/>
<property name="maximumRedeliveries" value="10"/>
<property name="useExponentialBackOff" value="false"/>
</bean>
</property>
</bean>
<bean id="connectionFactoryXA"
class="com.atomikos.jms.AtomikosConnectionFactoryBean"
init-method="init" destroy-method="close">
<property name="uniqueResourceName" value="amq1" />
<property name="xaConnectionFactory" ref="xaFactory" />
<property name="maxPoolSize" value="10" />
</bean>
<bean id="connectionFactory"
class="org.apache.activemq.pool.PooledConnectionFactory"
p:connectionFactory-ref="connectionFactorySingle" p:maxConnections="10"
/>
<amq:connectionFactory id="connectionFactorySingle"
messagePrioritySupported="true"
brokerURL="${jms.providerUrl}" userName="${jms.user}"
password="${jms.password}"/>
activemq.xml :
<policyEntry queue="dispatcher"
prioritizedMessages="true">
<deadLetterStrategy>
<individualDeadLetterStrategy queuePrefix="DLQ."
useQueueForQueueMessages="true" />
</deadLetterStrategy>
</policyEntry>
--
¸„ø¤º°☆°º¤ø„☆♥★
Giancarlo Frison
http://gfrison.com
http://boblink.com