hivemq-mqtt-client icon indicating copy to clipboard operation
hivemq-mqtt-client copied to clipboard

HiveMQ MQTT Client is an MQTT 5.0 and MQTT 3.1.1 compatible and feature-rich high-performance Java client library with different API flavours and backpressure support

Results 132 hivemq-mqtt-client issues
Sort by recently updated
recently updated
newest added

## Expected behavior HiveMQ android client should keep the connection to the broker alive with ping requests. ## Actual behavior HiveMQ android client doesn't send a ping request if the...

question

I am trying to simulate un-graceful disconnect and client takeover (in this case, the broker doesn't support it). Like to know how to re-establish the connection? I am not sure...

question

## Expected behavior After performing re-connect and re-subscription to MQTT broker callback is fired each time a new message arrives to the topic the client is subscribed to. ## Actual...

**Motivation** The traffic flow of the current version is hard to debug because there are no logs for e.g. which messages are sent and received. **Changes** Add additional logging Closes...

## Expected behavior Calling client.disconnect() should allow for gracefully program termination. The provided example creates an async client, connects and subscribes to a topic. Normal operation would expect the program...

## Expected behavior `connect()` fails even if configured to reconnect if it is determined that reconnect attempts will always fail. Case in point, attempts to connect to MQTT 3 only...

feature-request

Hello, i'm trying to create a publish message and then i want to encode it in the corresponding sequence of bytes, but I'm not able to use the encoding packages...

question

## Expected behavior Connect to the MQTT server with no problem and publish two messages, one with the topic AndroidApp and the other in publish function. Log: ``` D/MQttConnectionClass: connectTOmqtt:...

question

## Expected behavior After a client is reconnected by means of `context.getReconnector().reconnect(true)`, an already established subscription should continue working as it did before reconnecting the client. ## Actual behavior After...

invalid

## Expected behavior I didn't know how to report it but I can't find in the documentation how to set up a timeout while publishing a message. [Here](https://github.com/hivemq/hivemq-mqtt-client#consume-messages), it's described...