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
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.
|