hivemq-mqtt-client | HiveMQ MQTT Client is an MQTT | Websocket library

I'm using the HiveMQ library in my Java Spring application to connect to a Mosquitto instance as I find it more user-friendly compared to the Paho client. But something is going wrong with the automatic reconnection. From time to time the connection is lost and the application doesn't succeed in reconnecting (see logs 1). This can also be triggered by restarting the Mosquitto broker itself (see logs 2).

This is my client builder code with additional logging in the disconnect to check if the credentials are still correct:

In a Java server application, we want to use the correlationData, which is part of MQTT5, so we can use this in the reply message to link and validate it when the reply is received.

I'm using the hivemq-mqtt-client library 1.2.2 and connecting to HiveMQ Cloud.

The connection is made like this:

I am relatively new to MQTT and am trying to connect via a websocket in my Android app.

HiveMQ and Paho seem to be the most commonly used libraries, so I'll try my luck with those for now.

Unfortunately I got right at the first library and would need a hint on how to proceed, as the docs don't say anything about this unfortunately. With HiveMQ, it's not entirely clear to me how to connect via websocket, and how to customize my credentials/headers, because I need to add some custom header like "x-amz-customauthorizer-name" and some more.

This is my attempt without adding the user credentials:

I keep getting the error from the title while trying to push to docker via GitHub Actions. I have a Java Maven application. When I build and push the docker image manually everything works but it does not work automatically via GitHub Actions as specified in the title.

Here is my workflow action:

Is there a built in way to check with hivemq-mqtt-client if a specific topic matches another topic in advance?

For instance, a message published with topic:

publishedTopic= "sensors/sensor1";

A client that subscribes:

subscribedTopic = "sensors/#";

Is there something like publishedTopic.matches(subscribedTopic)?

The exact situation:

I run a broker in my house, several devices publish values with different topics. Some like sensor/humi[45], some like sensor/data[JSON Payload]. For my personal use I run an application using Java HiveQM MQTT clients. One client is subscribed to relevant topics using mosquitto on raspberryPi. The other client is publishing selected data to a public accessible broker. Receiving a new message will not only process all data in the way I process it but also trigger a publishing the received message to the public broker.

Yes, I can

we are currently switching form an older version of Eclipe Paho MQTT Client to Version 1.2 of HiveMQ MQTT Client. https://github.com/hivemq/hivemq-mqtt-client

Currently playing around with the Aync- version of the client which needs a Consumer function as a callback.

One of our MQTT Client Applications has to process/consumer a lot messages on many different topics and the processing of one message should not have to wait for the previous to finish. We are not sure what's the best way to achieve parallel processing of messages with only one client instance.

In the documentation above there is an optional executor that can be defined