You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by "sumit.wattal" <su...@gmail.com> on 2014/09/10 19:38:11 UTC
JMS Exception in dlqDeliveryFailureCause
Lately we are seeing lot of messages getting into the DLQ in our ActiveMQ
installation. We have a system based on ActiveMQ 5.6 and see tens of
millions of messages flowing through ActiveMQ daily. The messages in DLQ
belong to a particular queue which uses Transacted Ack mode and the failure
cause for these messages is javax.jms.JMSException: Duplicate dispatch with
transacted redeliver pending on another consumer, connection.
I am not very sure what the error message suggests. Would really appreciate
any help on this.
Thanks,
SW
--
View this message in context: http://activemq.2283324.n4.nabble.com/JMS-Exception-in-dlqDeliveryFailureCause-tp4685459.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: JMS Exception in dlqDeliveryFailureCause
Posted by Gary Tully <ga...@gmail.com>.
I think the pool induced issue is resolved by
https://issues.apache.org/jira/browse/AMQ-5226
On 12 September 2014 15:28, James Black <be...@yahoo.co.uk> wrote:
> I have just encountered the above problem after starting to use the latest
> connection pool. Out of 10,000 messages in our tests we saw 10 going onto
> the DLQ and it did not take long for this to occur.
>
> <dependency>
> <groupId>org.apache.activemq</groupId>
> <artifactId>activemq-pool</artifactId>
> <version>5.10.0</version>
> </dependency>
>
> This was addressed by moving back to using the previous connection pool
> version: 5.9.1.
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/JMS-Exception-in-dlqDeliveryFailureCause-tp4685459p4685507.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
--
http://redhat.com
http://blog.garytully.com
Re: JMS Exception in dlqDeliveryFailureCause
Posted by James Black <be...@yahoo.co.uk>.
I have just encountered the above problem after starting to use the latest
connection pool. Out of 10,000 messages in our tests we saw 10 going onto
the DLQ and it did not take long for this to occur.
<dependency>
<groupId>org.apache.activemq</groupId>
<artifactId>activemq-pool</artifactId>
<version>5.10.0</version>
</dependency>
This was addressed by moving back to using the previous connection pool
version: 5.9.1.
--
View this message in context: http://activemq.2283324.n4.nabble.com/JMS-Exception-in-dlqDeliveryFailureCause-tp4685459p4685507.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: JMS Exception in dlqDeliveryFailureCause
Posted by Gary Tully <ga...@gmail.com>.
I think what you are seeing is something that was resolved in the past
week - have a read of https://issues.apache.org/jira/browse/AMQ-5279
On 10 September 2014 18:38, sumit.wattal <su...@gmail.com> wrote:
> Lately we are seeing lot of messages getting into the DLQ in our ActiveMQ
> installation. We have a system based on ActiveMQ 5.6 and see tens of
> millions of messages flowing through ActiveMQ daily. The messages in DLQ
> belong to a particular queue which uses Transacted Ack mode and the failure
> cause for these messages is javax.jms.JMSException: Duplicate dispatch with
> transacted redeliver pending on another consumer, connection.
>
> I am not very sure what the error message suggests. Would really appreciate
> any help on this.
>
> Thanks,
> SW
>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/JMS-Exception-in-dlqDeliveryFailureCause-tp4685459.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
--
http://redhat.com
http://blog.garytully.com