[jira] [Commented] (AMQ-9175) MessageDelivered advisory causes NPE on non persistent broker when using transactions

["ASF subversion and git services (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMQ-9175?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17636751#comment-17636751 ] 

ASF subversion and git services commented on AMQ-9175:
------------------------------------------------------

Commit f83c5f1ba156ed850acf76dc42f944b4150d21f8 in activemq's branch refs/heads/main from Christopher L. Shannon (cshannon)
[ https://gitbox.apache.org/repos/asf?p=activemq.git;h=f83c5f1ba ]

AMQ-9175 - Properly set broker on ConnectionContext inside
MemoryTransactionStores

This fixes a NPE when using the messageDelivered advisory and
transactions


> 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)