[jira] [Commented] (AMQ-2594) Make JDBC store resilient on broker sequence id order

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMQ-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15420828#comment-15420828 ] 

ASF subversion and git services commented on AMQ-2594:
------------------------------------------------------

Commit 6d44ae6e971a341217c6f5a8669900740654b0ab in activemq's branch refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=6d44ae6 ]

AMQ-5815 - remove obsolete remnant of fix for AMQ-2594. holding global lock before attempting to get index and checkpoint lock can lead to deadlock if checkpoint write lock request pops in


> Make JDBC store resilient on broker sequence id order
> -----------------------------------------------------
>
>                 Key: AMQ-2594
>                 URL: https://issues.apache.org/jira/browse/AMQ-2594
>             Project: ActiveMQ
>          Issue Type: Improvement
>    Affects Versions: 5.3.0
>            Reporter: Dejan Bosanac
>            Assignee: Dejan Bosanac
>             Fix For: 5.3.1, 5.4.0
>
>         Attachments: AMQ-2594.work-in-progress.patch
>
>
> Currently if the message is sent in a transaction, there's a chance that messages are added to the cursor out of order (regarding broker seq id). The problem with JDBC store is that it does message recovery based on this seq id, which can lead to all kind of problems (such as orphaned messages in the database).
> The solution is to refactor JDBC store to use its own seq generator for recovering purposes and replace broker seq id, with message id for all other operations



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)