[
https://issues.apache.org/jira/browse/ARTEMIS-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16630872#comment-16630872
]
ASF GitHub Bot commented on ARTEMIS-1874:
-----------------------------------------
Github user clebertsuconic commented on the issue:
https://github.com/apache/activemq-artemis/pull/2336
@rpelisse what is the commit ID upstream? can you use cherry-pick -x (or
amend the commit with the full hash?)
example from another commit:
```
commit 19998d310f143ad5370683db42c63f64b43ee338
Author: Justin Bertram <[email protected]>
Date: Wed Sep 26 14:27:14 2018 -0500
ARTEMIS-2098 potential NPE when decoding protocol
(cherry picked from commit c72bf53cb178d2d9d310f3f369c0cbdb22e6f50c)
```
> NPE in ActiveMQMessage.setObjectProperty
> ----------------------------------------
>
> Key: ARTEMIS-1874
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1874
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.6.0
> Reporter: Alastair Mailer
> Assignee: Justin Bertram
> Priority: Critical
> Fix For: 2.6.1, 2.7.0
>
>
> Calling ActiveMQMessage.setObjectProperty("name", null) causes an NPE in
> handleCoreProperty line 968 (value.toString()) if "name" is either
> "JMSXGroupID" or "JMSXUserID".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
