Issue Details (XML | Word | Printable)

Key: JMS_SPEC-117
Type: New Feature New Feature
Status: Open Open
Priority: Major Major
Assignee: Nigel Deakin
Reporter: Nigel Deakin
Votes: 0
Watchers: 1

If you were logged in you would be able to see more operations.

Specifying redelivery behaviour when a JMS MDB performs rollback

Created: 21/Mar/13 04:30 PM   Updated: 02/Apr/13 09:30 AM
Component/s: None
Affects Version/s: 1.1, 2.0
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:

Tags: jms21-forreview-major
Participants: Nigel Deakin

 Description  « Hide

It may be helpful if the spec defined what should happen if a JMS MDB receives a message and then rolls back the transaction, typically because setRollbackOnly has been called. If the rollback is caused by a system error (such as a database failure) then the same message might be redelivered and rolled back repeatedly.

Possible behaviour that might be required is:

  • A delay before the message is redelivered - perhaps increasing as the number of redelivery attempts increases
  • A maximum number of consecutive rollbacks after which the message will be delivered to a dead-message queue

No doubt there are other possibilities.

It would of course be necessary to allow this behaviour to be configured, perhaps using activation properties.

Sort Order: Ascending order - Click to sort in descending order
amyk made changes - 21/Mar/13 06:15 PM
Field Original Value New Value
Link This issue is duplicated by MQ-220 [ MQ-220 ]