You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Matt Pavlovich (Jira)" <ji...@apache.org> on 2022/02/16 20:52:00 UTC

[jira] [Reopened] (AMQ-5536) Inconsistent Behavior for Duplicate Message Handling

     [ https://issues.apache.org/jira/browse/AMQ-5536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Pavlovich reopened AMQ-5536:
---------------------------------

> Inconsistent Behavior for Duplicate Message Handling
> ----------------------------------------------------
>
>                 Key: AMQ-5536
>                 URL: https://issues.apache.org/jira/browse/AMQ-5536
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 5.9.1, 5.10.1
>         Environment: OS X Yosemite, jdk 1.7
>            Reporter: Michael Rimov
>            Assignee: Matt Pavlovich
>            Priority: Major
>              Labels: bug, close-pending, jdbc
>         Attachments: ActiveMQ-Tests.zip
>
>
> Unlike Kahia, JDBC Persistence adapters allow duplicate ID's into the dead letter queue.  I've included a test showing the difference between Kahia and two different jdbc persistence stores. (MySQL and H2)
> In JDBC persistence environments this eventually shows up as errors asking if the audit cursor is enabled, and in older versions (5.9.1, 5.10.0) can cause deadlocks.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)