Description
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
Attachments
Attachments
Issue Links
- relates to
-
AMQ-5815 Frequency IOException cast dead lock while using kahadb in high concurrency environment
-
- Resolved
-