[
https://issues.apache.org/jira/browse/AMQ-9175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17636756#comment-17636756
]
ASF subversion and git services commented on AMQ-9175:
------------------------------------------------------
Commit 20dc305a49c0538ef743043f12f3d075694c693f in activemq's branch
refs/heads/activemq-5.17.x from Christopher L. Shannon (cshannon)
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=20dc305a4 ]
AMQ-9175 - Properly set broker on ConnectionContext inside
MemoryTransactionStores
This fixes a NPE when using the messageDelivered advisory and
transactions
(cherry picked from commit f83c5f1ba156ed850acf76dc42f944b4150d21f8)
> MessageDelivered advisory causes NPE on non persistent broker when using
> transactions
> -------------------------------------------------------------------------------------
>
> Key: AMQ-9175
> URL: https://issues.apache.org/jira/browse/AMQ-9175
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 5.17.2
> Reporter: Christopher L. Shannon
> Assignee: Christopher L. Shannon
> Priority: Major
> Fix For: 5.18.0, 5.17.3
>
>
> I was doing some more testing and noticed that in the tests when using a non
> persistent broker (MemoryTransactionStore) there is a null pointer exception
> thrown when MessageDelivered is turned on as the ConnectionContext used by
> the transaction store does not set the broker like it should on the object.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
