[ https://issues.apache.org/jira/browse/ARTEMIS-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
gongping.zhu reopened ARTEMIS-4519: ----------------------------------- A third-party mqtt client successfully connects to ActiveMQ Artemis. The server generates two sessions, one for regular client operations and the other for internal management operations. Based on your conclusion, I tracked and reviewed the source code and found that the session names used for internal management start with management::, but none of them I saw in the web management console, And there are no sessions starting with management:: on the backend log, what's going on? Can anyone help answer this? > Why can a client connect and see two different session IDs on the console? > -------------------------------------------------------------------------- > > Key: ARTEMIS-4519 > URL: https://issues.apache.org/jira/browse/ARTEMIS-4519 > Project: ActiveMQ Artemis > Issue Type: Bug > Components: MQTT > Affects Versions: 2.31.2 > Reporter: gongping.zhu > Priority: Major > Attachments: image-2023-11-30-11-00-08-171.png > > > Why can a client connect and see two different session IDs on the console? > After a successful client connection, it will call before Create Session > twice, with the same connId but different sessions? > -- This message was sent by Atlassian Jira (v8.20.10#820010)