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/04/26 11:56:00 UTC

[jira] [Commented] (AMQ-7189) 'native' inbound transformer can mishandle AMQP durable field, classify non-durable message as persistent

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

ASF subversion and git services commented on AMQ-7189:
------------------------------------------------------

Commit aff9413cdbe88041552369787d1ba001c2b4ffd4 in activemq's branch refs/heads/master from Robert Gemmell
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=aff9413 ]

AMQ-7189: ensure messages with defauled durable field are internally classed non-persistent by the 'native' transformer


> 'native' inbound transformer can mishandle AMQP durable field, classify non-durable message as persistent
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-7189
>                 URL: https://issues.apache.org/jira/browse/AMQ-7189
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: AMQP
>    Affects Versions: 5.15.9
>            Reporter: Robbie Gemmell
>            Assignee: Robbie Gemmell
>            Priority: Major
>             Fix For: 5.15.10
>
>
> If an AMQP message arrives that has a header section but defaults the durable field within it in (meaning the message is non-durable), the brokers 'native' transformer incorrectly classifies the message as being persistent. The issue is only visible inside the broker, the consumed message correctly indicates it was non-durable. The 'jms' transformer is not affected.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)