qpid-proton mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robbie Gemmell (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PROTON-474) Incorrect mapping of TTL to JMSExpiration in JMS InboundTransformer
Date Wed, 02 Jul 2014 15:10:25 GMT

     [ https://issues.apache.org/jira/browse/PROTON-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Robbie Gemmell updated PROTON-474:
----------------------------------

    Attachment: PROTON-474-v3.patch

Attaching PROTON-474-v3.patch

Changes to InboundTransformer are as previously, changes to JMSMappingOutboundTransformer
updated based on above discussion. If JMSExpiration is not 0, absolute-expiry-time is set
to match, and TTL is set to current-expiration or 1 if that proves negative due to the possible
race since deciding to send the message.

> 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
>            Assignee: Robbie Gemmell
>             Fix For: 0.8
>
>         Attachments: JMSExpiration-patch.txt, PROTON-474-v2.patch, PROTON-474-v3.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.2#6252)

Mime
View raw message