Sounds like it could be a bug. Please file a JIRA bug report:
http://issues.apache.org/activemq/browse/AMQ
If a small test case accompanied that bug report, it would expedite
figuring out what's happening.
On 5/24/06, Christopher G. Stach II <[EMAIL PROTECTED]> wrote:
Christopher G. Stach II wrote:
> org.apache.activemq.broker.AbstractConnection.serviceException Async
> error occurred: javax.jms.JMSException: Could not correlate
> acknowledgment with dispatched message: MessageAck {commandId = 137,
James:
I don't quite understand this. According to
http://www.activemq.org/site/message-redelivery-and-dlq-handling.html, a
poison ack is only sent when all redelivery attempts have failed. I
have redelivery configured in two places, on the client side on the MCF
(the location where that wiki page states it should be) and on the RA to
be sure, but the poison ack comes back immediately. I get no
redeliveries at all.
<bean id="jms.connectionFactory"
class="org.springframework.jca.support.LocalConnectionFactoryBean">
<property name="connectionManager">
<bean
class="com.xxx.jca.ResinConnectionManagerFactoryBean">
<property name="localTransaction">
<value>false</value>
</property>
<property name="localTransactionOptimization">
<value>false</value>
</property>
<property name="managedConnectionFactory">
<ref local="jms.managedConnectionFactory"
/>
</property>
<property name="xaTransaction">
<value>true</value>
</property>
</bean>
</property>
<property name="managedConnectionFactory">
<ref local="jms.managedConnectionFactory" />
</property>
</bean>
<bean id="jms.jcaContainer" class="org.jencks.JCAContainer">
<property name="bootstrapContext">
<bean class="com.xxx.jca.ResinBootstrapContextFactoryBean"
/>
</property>
<property name="resourceAdapter">
<ref local="jms.resourceAdapter" />
</property>
</bean>
<bean id="jms.managedConnectionFactory"
class="org.apache.activemq.ra.ActiveMQManagedConnectionFactory">
<property name="allPrefetchValues">
<value>1</value>
</property>
<property name="initialRedeliveryDelay">
<value>2000</value>
</property>
<property name="maximumRedeliveries">
<value>9</value>
</property>
<property name="redeliveryBackOffMultiplier">
<value>2</value>
</property>
<property name="redeliveryUseExponentialBackOff">
<value>true</value>
</property>
<property name="resourceAdapter">
<ref local="jms.resourceAdapter" />
</property>
</bean>
<bean id="jms.broker"
class="org.apache.activemq.xbean.BrokerFactoryBean">
<property name="config">
<value>classpath:activemq.xml</value>
</property>
<property name="start">
<value>true</value>
</property>
</bean>
<bean id="jms.resourceAdapter"
class="org.apache.activemq.ra.ActiveMQResourceAdapter"
depends-on="jms.broker">
<property name="allPrefetchValues">
<value>1</value>
</property>
<property name="initialRedeliveryDelay">
<value>2000</value>
</property>
<property name="maximumRedeliveries">
<value>9</value>
</property>
<property name="redeliveryBackOffMultiplier">
<value>2</value>
</property>
<property name="redeliveryUseExponentialBackOff">
<value>true</value>
</property>
<property name="serverUrl">
<value>vm://localhost</value>
</property>
</bean>
Is this just misconfiguration or a bug? It's preventing us from moving
forward at all with 4.0.
--
Christopher G. Stach II
--
Regards,
Hiram
