[
https://issues.apache.org/jira/browse/ARTEMIS-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17720787#comment-17720787
]
Liviu Citu edited comment on ARTEMIS-2824 at 5/9/23 5:28 AM:
-------------------------------------------------------------
Seems good. Thank you!
If not too much effort I think we will need the same change also for the
initial reported notification type (SESSION_CLOSED)
I would say the client id should be also set for the following notification
types (at least):
* SESSION_CREATED
* SESSION_CLOSED
Nice to have:
* BINDING_REMOVED
* BINDING_ADDED
But again if too much effort then no need. As far as I am concern, what you
have done is sufficient.
Thanks again.
was (Author: JIRAUSER300236):
Seems good. Thank you!
> _AMQ_Client_ID on SESSION_CLOSED notification is always null
> ------------------------------------------------------------
>
> Key: ARTEMIS-2824
> URL: https://issues.apache.org/jira/browse/ARTEMIS-2824
> Project: ActiveMQ Artemis
> Issue Type: Bug
> Affects Versions: 2.11.0
> Reporter: Tim Daly
> Assignee: Justin Bertram
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> When a JMS client with a clientId set closes the session a notification
> (_AMQ_NotifType=SESSION_CLOSED) is sent by the broker but the _AMQ_Client_ID
> is always set to null. The JMS Client Id has been verified as being set via
> the web UI.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
