[ https://issues.apache.org/jira/browse/PROTON-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hiram Chirino updated PROTON-474: --------------------------------- Attachment: PROTON-474.patch Attaching updated patch that also does a similar mapping on the outbound side. > Incorrect mapping of TTL to JMSExpiration in JMS InboundTransformer > ------------------------------------------------------------------- > > Key: PROTON-474 > URL: https://issues.apache.org/jira/browse/PROTON-474 > Project: Qpid Proton > Issue Type: Bug > Components: proton-j > Affects Versions: 0.5 > Reporter: Timothy Bish > Fix For: 0.7 > > Attachments: JMSExpiration-patch.txt, PROTON-474.patch > > > 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. -- This message was sent by Atlassian JIRA (v6.1.5#6160)