[
https://issues.apache.org/jira/browse/ARTEMIS-4519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17791417#comment-17791417
]
gongping.zhu edited comment on ARTEMIS-4519 at 11/30/23 3:02 AM:
-----------------------------------------------------------------
when i nomally use ./artemis create /var/www/html/brokers/node3 to create
instance;and then use ./artemis run; after zhe broker started,i use zhe third
mqtt client to connect zhe broker, and login zhe web admin console,you can see
this one connect has two different session
!image-2023-11-30-11-00-08-171.png!
was (Author: JIRAUSER293605):
when i nomally use ./artemis create /var/www/html/brokers/node3 to create
instance;and then use ./artemis run; after zhe broker started,i use zhe third
mqtt client to connect zhe broker, and login zhe web admin console,you can see
this
!image-2023-11-30-11-00-08-171.png!
> 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)
