Silvio Giebl

@deen13 this was not intended. It seems to be an auto reply to some mails.

Hi @NuwanSameera The keystore used for the trustmanager should contain only the CA cert. The keystore used for the keymanager should contain only the client cert and key. Also, can...

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 @amindadgar Sorry for the delayed response. You seam to use SSL/TLS (`.sslWithDefaultConfig()`) but connect to port 1883. MQTT over SSL/TLS usually uses port 8883. This might be the cause...

Hi @StevenYan88 It seems that you are on Android. Please follow this guide: https://hivemq.github.io/hivemq-mqtt-client/docs/installation/android/ If that does not work, please provide more information (for example Android build tool versions)

Hi @smaugs Sorry for the delayed response. > when the publish flow dies (for whatever reason) You probably refer to the reactive API and that the flow is cancelled inside...

Hi @smaugs I may have a solution to your problem that is already possible: You can add a "fallback" flow, that consumes all messages for which no other flow exists....

We should probably make it configurable whether the client should disconnect if it receives a message without a flow. Added this issue to the 2.0 milestone if we want to...

Hi @FrVaBe This is definitely a feature that we want to integrate in the automatic reconnect feature. In the meantime you can already implement (re)connecting to different broker addresses on...

Hi @degill Yes, you can add a DisconnectedListener and set reconnect to false, for example: ```java final AtomicBoolean cancelReconnect = new AtomicBoolean(false); Mqtt5Client.builder() .automaticReconnectWithDefaultConfig() .addDisconnectedListener(context -> { if (cancelReconnect.get()) {...