Silvio Giebl

Hi @missourian55 If you use `automaticReconnect`, then there is no reason to call `if (!isConnected) { disconnect; connect; }` yourself. Currently, the client does not support disconnecting and reconnecting yourself...

@missourian55 sorry for the delayed response. I don't know how Solace handles reconnects/client takeovers and so on. To see if the server rejects reconnect attempts, please add a ConnectedListener and...

This was actually intended. We should discuss what the default behavior should be. You can work around in the mean time: ```java Mqtt5Client.builder() ... .automaticReconnectWithDefaultConfig() .addDisconnectedListener(context -> { if (context.getClientConfig().getState()...

Hi @mathieuruellan This happens because the newer gradle version automatically uses gradle module metadata instead of the maven pom and the websocket module is a pom-only artifact. The following works:...

Sorry for the inconvenience. Now there is a hint in the documentation and in the readme.

@cla-bot check

@Sarek You need to sign our CLA before we can review your PR. You'll find the CLA and more information here: https://github.com/hivemq/hivemq-community/blob/master/CONTRIBUTING.adoc#contributor-license-agreement And sorry that you need to rebase your...

Sorry for the delay, I will still answer here in the next few days, but unfortunately did not find the time in the last weeks.

Hi @digrec Thank you for the detailed description. > Why does the packet ID never increment or change The MQTT specification does not specify that packet ids must be incremented...

Hi @symphonybiz Can you provide more details, like a full stack trace or logs from the build?