The HiveMQ team is pleased to announce the availability of HiveMQ 3.2.7. This is a maintenance release for the 3.2 series and brings the following improvements:
- Added logging of the replication state when a node joins a cluster
- Fixed a reference counting issue
- Fixed an issue that could cause a client to not receive queued messages until it reconnects again
- Fixed an issue that could cause other subscriptions to be removed for the same client if an unsubscribe message is sent to the wildcard topic
- Fixed an issue that caused clients to not be able to change the QoS for their subscriptions
- Fixed an rare issue that could cause a client to not receive any messages after a successful connection
- Fixed an cosmetic issue that caused IOExceptions to be wrongfully logged when a client disconnected
- Fixed an issue that could cause HiveMQ to not shut down properly when a plugin triggers a shutdown via UnrecoverableExceptions
- Fixed an issue that could cause cluster nodes to not be operational on startup
- Fixed verbose RESTService logging
- Fixed an issue that could cause messages to be queued although there is no need to queue them
- Fixed an issue that could lead to incorrect subscription count metrics
- Fixed an issue that could cause the loss of retained messages when using the stateful-cluster.sh script
You can download the new HiveMQ version here.
We strongly recommend to upgrade if you are an HiveMQ 3.2.x user.
Have a great day, The HiveMQ Team