You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the client gets disconnected in the client context the cli should inform the user that the current context client is no longer available and change the context back to shell-context.
Actual behavior
The context client is shown, even though it got disconnected, and if a command with that client is used it will throw an error.
To Reproduce
In one terminal 1: hivemq-cli shell con -i client client>
In terminal 2: hivemq-cli shell con -i client
E. g. hivemq will produce: Disconnecting already connected client with id client because another client connects with that id client>
In terminal 1: client> still shown, but it's actually not connected anymore. client> pub -t topic -m msg will throw PUBLISH to topic failed with MQTT client is not connected.
Details
Affected HiveMQ CLI version(s): 1.0
Used JVM version: 11
The text was updated successfully, but these errors were encountered:
Expected behavior
If the client gets disconnected in the client context the cli should inform the user that the current context client is no longer available and change the context back to shell-context.
Actual behavior
The context client is shown, even though it got disconnected, and if a command with that client is used it will throw an error.
To Reproduce
In one terminal 1:
hivemq-cli shell
con -i client
client>
In terminal 2:
hivemq-cli shell
con -i client
E. g. hivemq will produce:
Disconnecting already connected client with id client because another client connects with that id
client>
In terminal 1:
client>
still shown, but it's actually not connected anymore.client> pub -t topic -m msg
will throwPUBLISH to topic failed with MQTT client is not connected.
Details
The text was updated successfully, but these errors were encountered: