[PROTON-474] Incorrect mapping of TTL to JMSExpiration in JMS InboundTransformer

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: proton-0.5
• Fix Version/s: proton-0.8
• Component/s: proton-j
• Assignee: Robbie Gemmell
• Reporter: Timothy A. Bish
• Created: 03/Dec/13 22:49
• Updated: 07/Jan/16 11:37
• Resolved: 02/Jul/14 15:21

Description

The inbound message transformation of AMQP message to JMS message incorrectly sets the JMSExpiration to message TTL which is defined in milliseconds while the JMSExpiration value is a sum of the Message Timestamp and the producers TTL. The transformation should probably map the message creation time + the TTL to the setJMSExpiration method.

Issue Links

• is depended upon by: AMQ-5002 AMQP: If a proton client only sets the ttl, and not the message timestamp, ActiveMQ does not handle the expiration correctly
• is related to: AMQ-5403 remove extra expiration and timestamp manipulaton which will cause problems