You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@activemq.apache.org by "Robbie Gemmell (JIRA)" <ji...@apache.org> on 2019/04/26 12:09:00 UTC

[jira] [Updated] (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:all-tabpanel ]

Robbie Gemmell updated AMQ-7189:
--------------------------------
    Description: 
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.

Background: https://lists.apache.org/thread.html/cf8d0f0ca6b232a8a447d984b27edc0fe58a7cc2e5a76f8c7e5e6cca@%3Cusers.qpid.apache.org%3E

  was: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.


> '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.
> Background: https://lists.apache.org/thread.html/cf8d0f0ca6b232a8a447d984b27edc0fe58a7cc2e5a76f8c7e5e6cca@%3Cusers.qpid.apache.org%3E



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