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

Posted to issues@activemq.apache.org by "clebert suconic (Jira)" <ji...@apache.org> on 2019/08/26 15:45:02 UTC

[jira] [Closed] (ARTEMIS-2390) JMSMessageID header can be null when messages are cross-protocol

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

clebert suconic closed ARTEMIS-2390.
------------------------------------
    Resolution: Fixed

> JMSMessageID header can be null when messages are cross-protocol
> ----------------------------------------------------------------
>
>                 Key: ARTEMIS-2390
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2390
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 2.9.0
>            Reporter: Howard Gao
>            Assignee: Howard Gao
>            Priority: Major
>             Fix For: 2.10.0
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> If a jms client (be it openwire, amqp, or core jms) receives a message that is from a different protocol, the JMSMessageID maybe null when the jms client expects it.



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