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 subversion and git services (Jira)" <ji...@apache.org> on 2019/08/27 05:41:00 UTC

[jira] [Commented] (AMQNET-607) It should be possible to reset AbsoluteExpiryTime

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

ASF subversion and git services commented on AMQNET-607:
--------------------------------------------------------

Commit b606b6282961b60e28af07d7aeb2c70496528021 in activemq-nms-amqp's branch refs/heads/master from Michael André Pearce
[ https://gitbox.apache.org/repos/asf?p=activemq-nms-amqp.git;h=b606b62 ]

Merge pull request #22 from Havret/reset_absolute_expiry_time

AMQNET-607: It should be possible to reset AbsoluteExpiryTime

> It should be possible to reset AbsoluteExpiryTime
> -------------------------------------------------
>
>                 Key: AMQNET-607
>                 URL: https://issues.apache.org/jira/browse/AMQNET-607
>             Project: ActiveMQ .Net
>          Issue Type: Improvement
>          Components: AMQP, NMS
>    Affects Versions: 1.8.0
>            Reporter: Krzysztof Porebski
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> There is no way to reset AbsoluteExpiryTime field on Message properties once set. It used to be impossible to implement due to limitations of amqpnetlite. Once new version was released, it could be fixed.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)