[ https://issues.apache.org/jira/browse/AMQ-7298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16922424#comment-16922424 ]
ASF subversion and git services commented on AMQ-7298: ------------------------------------------------------ Commit f155e92e58da5882ff83414cbe31abad6e4e2e26 in activemq's branch refs/heads/master from gtully [ https://gitbox.apache.org/repos/asf?p=activemq.git;h=f155e92 ] AMQ-7298 - use final modifier in test to preserve older jdk builds > failover duplicate detection in error with batched local transactions > --------------------------------------------------------------------- > > Key: AMQ-7298 > URL: https://issues.apache.org/jira/browse/AMQ-7298 > Project: ActiveMQ > Issue Type: Bug > Components: JMS client > Affects Versions: 5.15.0 > Reporter: Gary Tully > Assignee: Gary Tully > Priority: Major > Fix For: 5.16.0 > > > Messages can get poisonAcked in error as duplicate deliveries when a local > transaction rollback during/after a failover (auto reconnect) event. > The interaction between rollback and failover redelivery has a bunch of > timing issues and did create duplicates in-error that resulted in over eager > suppression. > There are a bunch of related tests that validate expected behaviour, the > related fixes needed to be revisited to better manage the delivered and > unconsumed messages in the context of a local transaction and to avoid the > real duplication of delivery in the client. > There is an additional new test that demonstrates the additional dlq or > duplicates behaviour. > a nice cross section from the unit test suite is: > mvn clean install > -Dtest=CloseRollbackRedeliveryQueueTest,AMQ2149Test,JMSQueueRedeliverTest,RedeliveryPolicyTest,FailoverTransactionTest,FailoverDurableSubTransactionTest,JMSConsumerTest,JmsSessionRecoverTest,AMQ2751Test -- This message was sent by Atlassian Jira (v8.3.2#803003)