[PROTON-704] delivery-count is set incorrectly during outbound transformation

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: proton-0.7
• Fix Version/s: proton-0.8
• Assignee: Robbie Gemmell
• Reporter: Robbie Gemmell
• Created: 30/Sep/14 13:20
• Updated: 07/Jan/16 11:37
• Resolved: 30/Sep/14 13:24

Description

In the proton-jms contrib artifact, delivery-count is set incorrectly (based on JMSXDeliveryCount) during outbound JMS message transformation.

The value set is the same as the JMSXDeliveryCount value encountered, which is incorrect as the two have different semantics. The delivery-count field in the AMQP 1.0 message header tracks prior unsuccessful delivery attempts and so should go 0,1,2 etc if set. JMSXDeliveryCount property in JMS tracks the total number of delivery attempts, and should go 1,2,3. As such, delivery-count should be 1 less than JMSXDeliveryCount, not equal to it.

Issue Links

• is cloned by: PROTON-715 [contrib/proton-jms] delivery-count is set incorrectly during Native outbound transformation