You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/03/15 20:27:41 UTC

[jira] [Commented] (ARTEMIS-1041) AMQP: Broker not respecting absolute expiry time

    [ https://issues.apache.org/jira/browse/ARTEMIS-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15926922#comment-15926922 ] 

ASF GitHub Bot commented on ARTEMIS-1041:
-----------------------------------------

GitHub user tabish121 opened a pull request:

    https://github.com/apache/activemq-artemis/pull/1096

    ARTEMIS-1041 Apply absolute expiration time to message

    Use the Absolute Expiration Time from the message properties and
    override any value set in TTL if anything set there.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/tabish121/activemq-artemis ARTEMIS-1041

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/1096.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1096
    
----
commit 5d434b1fd6c2a6c8a3e4f939aede4486a5060481
Author: Timothy Bish <ta...@gmail.com>
Date:   2017-03-15T20:25:40Z

    ARTEMIS-1041 Apply absolute expiration time to message
    
    Use the Absolute Expiration Time from the message properties and
    override any value set in TTL if anything set there.

----


> AMQP: Broker not respecting absolute expiry time
> ------------------------------------------------
>
>                 Key: ARTEMIS-1041
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1041
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: AMQP
>    Affects Versions: 2.0.0
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 2.next
>
>
> The update to the protocol handling in 2.0.0 are causing the absolute expiry time setting in incoming messages from being used to control message expiration lead to message not expiring when they should.  



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)