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

ASF subversion and git services commented on ARTEMIS-2390:
----------------------------------------------------------

Commit 2a84a6fd22dbfde96ac475be47aee30a3020ed77 in activemq-artemis's branch 
refs/heads/master from Clebert Suconic
[ https://gitbox.apache.org/repos/asf?p=activemq-artemis.git;h=2a84a6f ]

ARTEMIS-2390 Small improvement on UUID Conversion


> 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: 1h 20m
>  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
(v7.6.3#76005)

Reply via email to