[
https://issues.apache.org/jira/browse/BEAM-4182?focusedWorklogId=96371&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-96371
]
ASF GitHub Bot logged work on BEAM-4182:
----------------------------------------
Author: ASF GitHub Bot
Created on: 28/Apr/18 07:30
Start Date: 28/Apr/18 07:30
Worklog Time Spent: 10m
Work Description: matzew commented on issue #5238: BEAM-4182 fix to allow
JMSMessageId to be null
URL: https://github.com/apache/beam/pull/5238#issuecomment-385148969
@jbonofre mind taking a look here ?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 96371)
Time Spent: 20m (was: 10m)
> JMSMessageID can be null
> ------------------------
>
> Key: BEAM-4182
> URL: https://issues.apache.org/jira/browse/BEAM-4182
> Project: Beam
> Issue Type: Bug
> Components: io-java-jms
> Affects Versions: 2.4.0
> Reporter: Matthias Weßendorf
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> JMSRecord asssumes the JMSMessageID to be not null, but spec says:
>
> {quote}
> Message header field references are restricted to JMSDeliveryMode,
> JMSPriority, JMSMessageID, JMSTimestamp, JMSCorrelationID, and
> JMSType. JMSMessageID, JMSCorrelationID, and JMSType values may be
> null and if so are treated as a NULL value.
> {quote}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
