[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-dev
Subject:    [jira] [Updated] (AMQ-5032) AMQP Message Expiry Time not mapped correctly in many case to / from JMS
From:       "Timothy Bish (JIRA)" <jira () apache ! org>
Date:       2014-04-30 13:43:15
Message-ID: JIRA.12693585.1391702173057.206384.1398865395046 () arcas
[Download RAW message or body]


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

Timothy Bish updated AMQ-5032:
------------------------------

         Priority: Major  (was: Blocker)
    Fix Version/s:     (was: 5.10.0)
                   5.10.1

Proton is not accepting changes here for some reason.  Will push this out while we \
work with them to try and get this resolved in a future release.

> AMQP Message Expiry Time not mapped correctly in many case to / from JMS
> ------------------------------------------------------------------------
> 
> Key: AMQ-5032
> URL: https://issues.apache.org/jira/browse/AMQ-5032
> Project: ActiveMQ
> Issue Type: Bug
> Components: AMQP
> Affects Versions: 5.9.0
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Fix For: 5.10.1
> 
> 
> The message mapping done in Proton to convert to / from JMS messages is not \
> currently handling expiration time conversion correctly leading to message that \
> expire immediately or have no set expiration time etc.   Refer to: \
> https://issues.apache.org/jira/browse/PROTON-474



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[prev in list] [next in list] [prev in thread] [next in thread]