Ignoring MDB's activation-spec for RedeliveryInterval and RedeliveryAttempts (GLASSFISH-6617)

[GLASSFISH-18940] Add new property "imq.transaction.message.maxConsecutiveRollbacks" to glassfish jms service Created: 25/Jul/12  Updated: 20/Dec/16

Status: Open
Project: glassfish
Component/s: jms
Affects Version/s: None
Fix Version/s: 4.0_dev

Type: Sub-task Priority: Major
Reporter: David Zhao Assignee: Mike Fitch
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


Please update glassfish documentation for the enhancement of GLASSFISH-6617:

A new MQ 5.0 property "imq.transaction.message.maxConsecutiveRollbacks" was added.

For the EMBEDDED/LOCAL jms service of glassfish, the property can be set via admin gui:

Configurations -> server-config -> Java Message Service -> Additional Properties

For the REMOTE jms service of glassfish, the property should be set in the remote broker's config properties file.

Please refer to the MQ-134 and MQ-139 for the value of the property:

If <= 0, this feature is disabled;
If > 0, for running in GlassFish with JMSRA, when consecutive rollback a message to a consumer exceeds this number, the broker will automatically put this message to DMQ (if there are more than 1 message in the transaction, only the last message in the transaction is put to DMQ) and and rollback the rest of the transaction then return an error status to rollback

Generated at Sun Mar 26 14:22:37 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.