[
https://issues.apache.org/activemq/browse/AMQ-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Tully reassigned AMQ-2594:
-------------------------------
Assignee: Dejan Bosanac (was: Gary Tully)
Dejan, as I will be away for the next week and a bit, I am giving this back to
you, there is a new test case and some additions to your original work, but
there is still some detail to be finalized.
In particular, I think that we may want to have addMessage deal with
incrementing and assigning a brokerSequenceId when the message is persisted
(transaction actually committed), a change which will effect all stores.
Will chat during the week at some stage. thanks.
> Make JDBC store resilient on broker sequence id order
> -----------------------------------------------------
>
> Key: AMQ-2594
> URL: https://issues.apache.org/activemq/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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
