[
https://issues.apache.org/jira/browse/ARTEMIS-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Justin Bertram updated ARTEMIS-2390:
------------------------------------
Summary: JMSMessageID header can be null when messages are cross-protocol
(was: JMSMessageID header can be null when messages are cross-protocl)
> 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
>
>
> 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
(v7.6.3#76005)
