[
https://issues.apache.org/jira/browse/ARTEMIS-2390?focusedWorklogId=268502&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-268502
]
ASF GitHub Bot logged work on ARTEMIS-2390:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 27/Jun/19 12:42
Start Date: 27/Jun/19 12:42
Worklog Time Spent: 10m
Work Description: gaohoward commented on issue #2725: ARTEMIS-2390
JMSMessageID header can be null when messages are cross-protocol
URL: https://github.com/apache/activemq-artemis/pull/2725#issuecomment-506329421
Guys, I believe this is the old openwire behavior that the producer always
produces a messageID regardless of the disableMessageID flag.
My suggestion is to keep it as is for this PR.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 268502)
Time Spent: 1h (was: 50m)
> 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
> 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)
