Details
Description
I have no idea what is wrong but this makes reference to the following topics
http://old.nabble.com/No-redelivery-after-rollback-on-a-Topic-td28746372.html
Basically, rollback behavior is inconsistent:
- Works ok with a queue
- No redelivery on a topic with default settings
- No delivery at all with a consumer cache (from Spring's default message listener container)
- Delivery with a session cache but nothing get placed in the DLQ when the maximum number of re deliveries is reached
The project attached reproduces all uses cases in my environment (JTA and XA using bitronix)
Attachments
Attachments
1.
|
Uncaught exception in subscriber ends subscription | Resolved | Unassigned |