This issue was raised by a member of the JSR 343 Expert Group and is logged here to allow the issue to be discussed and tracked.
It is proposed that support for the JMS defined message property JMSXDeliveryCount be made mandatory.
The JMS 1.1 specification currently defines an optional JMS defined message property JMSXDeliveryCount. When used, this is set by the JMS provider when a message is received, and is set to the number of times this message has been delivered (including the first time). The first time is 1, the second time 2, etc.
Support for this property would allow arbitrary containers and applications to improve the way they handle "poisonous" messages - messages which cannot be consumed for some reason and need to be redelivered. For example, it would allow applications to detect when a message has been redelivered more than a specified number of times and perform some special handling such as redirecting it to some other destination.
This property wouldn't need to be perfectly accurate every time. For example, it wouldn't be necessary to persist this value in the server. A "best efforts" implementation would probably be adequately.
|Field||Original Value||New Value|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Assignee||Nigel Deakin [ nigeldeakin ]|
|Fix Version/s||2.0ED [ 16048 ]|
|Fix Version/s||2.0 [ 14692 ]|
|Resolution||Fixed [ 1 ]|