[
https://issues.apache.org/jira/browse/AMQ-6642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15950832#comment-15950832
]
ASF subversion and git services commented on AMQ-6642:
------------------------------------------------------
Commit bd083623dfbe98d025c31afa8471ad680922ba65 in activemq's branch
refs/heads/activemq-5.14.x from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=bd08362 ]
AMQ-6642: Fix potential NPE on updateMessage
Fixing potential NPE when calling updateMessage on a Queue store in
KahaDB if subscription statistics are enabled. Also reduced the
visibily from public to protected to subscription statistic related
methods that shouldn't be public and added null pointer checks there as
well.
https://issues.apache.org/jira/browse/AMQ-6642
(cherry picked from commit 2731f04f1ca81312d08ffc21c0ceb09513165b7c)
> MessageStore update message can encounter NPE with KahaDB
> ---------------------------------------------------------
>
> Key: AMQ-6642
> URL: https://issues.apache.org/jira/browse/AMQ-6642
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.14.4
> Reporter: Christopher L. Shannon
> Assignee: Christopher L. Shannon
> Fix For: 5.15.0, 5.14.5
>
>
> If KahaDB subscription statistics have been enabled (off by default) then
> it's possible to get a null pointer exception if updateMessage() is called on
> the message store. This occurs if the destination is a Queue as there is not
> a proper null pointer check done for ackPositions which only exists when
> using a Topic.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
