activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Rimov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMQ-5536) Inconsistent Behavior for Duplicate Message Handling
Date Fri, 23 Jan 2015 18:03:36 GMT

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

Michael Rimov updated AMQ-5536:
-------------------------------
    Attachment: ActiveMQ-Tests.zip

Set credentials.properties to use with mysql.

> 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
>              Labels: bug, 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
(v6.3.4#6332)

Mime
View raw message