-
Notifications
You must be signed in to change notification settings - Fork 234
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MQTT connection fails to reconnect in case of DDNS record IP adress change #2108
Comments
vvasilevbosch
added a commit
to bosch-io/ditto
that referenced
this issue
Feb 3, 2025
…ss should be resolved by ditto in mqtt connection Signed-off-by: Vasil Vasilev <[email protected]>
vvasilevbosch
added a commit
to bosch-io/ditto
that referenced
this issue
Feb 3, 2025
…ss should be resolved by ditto in mqtt connection Signed-off-by: Vasil Vasilev <[email protected]>
vvasilevbosch
added a commit
to bosch-io/ditto
that referenced
this issue
Feb 3, 2025
…ss should be resolved by ditto in mqtt connection Signed-off-by: Vasil Vasilev <[email protected]>
vvasilevbosch
added a commit
to bosch-io/ditto
that referenced
this issue
Feb 3, 2025
…ss should be resolved by ditto in mqtt connection Signed-off-by: Vasil Vasilev <[email protected]>
vvasilevbosch
added a commit
to bosch-io/ditto
that referenced
this issue
Feb 3, 2025
eclipse-ditto#2108: add possibility to configure whether server address should be resolved by ditto in mqtt connection Signed-off-by: Vasil Vasilev <[email protected]>
vvasilevbosch
added a commit
to bosch-io/ditto
that referenced
this issue
Feb 3, 2025
* add possibility to configure whether server address should be resolved by ditto in mqtt connection * fix retry timeout strategy unable increase retry count and apply effective backoff Signed-off-by: Vasil Vasilev <[email protected]>
thjaeckle
added a commit
that referenced
this issue
Feb 3, 2025
…rver-address #2108 MQTT Connection - add posibility to configure if server address should be resolved by ditto or on demand by mqtt client
thjaeckle
pushed a commit
that referenced
this issue
Feb 3, 2025
* add possibility to configure whether server address should be resolved by ditto in mqtt connection * fix retry timeout strategy unable increase retry count and apply effective backoff Signed-off-by: Vasil Vasilev <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
hivemq-mqtt-client uses java.net.InetSocketAddress for server address and caches it. Currently, ditto provides resolved InetSocketAddress, which is never re-resolved and not handled by the hivemq mqtt client. This causes mqtt connections to reconnect without success infinitely.
The text was updated successfully, but these errors were encountered: