HiveMQ 4.28.21 Maintenance Release
The HiveMQ team is pleased to announce the availability of HiveMQ 4.28.21.
This maintenance release for the 4.28 series includes the following improvements:
Anonymous Usage Statistics Change
NOTE: Starting with HiveMQ 4.28.21, the broker’s built-in anonymous usage tracking is enabled by default.
This data helps us understand how the product is used and guides future improvements to the HiveMQ platform.
If you prefer not to send anonymous usage data, you can explicitly disable the feature in your config.xml file:
...
<anonymous-usage-statistics>
<enabled>false</enabled>
</anonymous-usage-statistics>
...
If you previously removed this configuration to disable statistics, you must add the configuration with <enabled>false</enabled>to maintain the disabled status after upgrading to HiveMQ 4.28.21 or later.
- If no configuration is present, statistics are automatically enabled when you upgrade to version 4.28.21 or higher.
- For complete configuration details and a list of all data collected, see Anonymous Usage Statistics in our documentation.
HiveMQ Enterprise MQTT Broker
- Fixed a rare issue where client sessions could be incorrectly marked as offline after a cluster merge.
- Expanded the Diagnostic Archive to include metrics for up to 72 hours before the last graceful shutdown and start of the broker.
- Added limits to the number of parallel topology replication batches per node to improve cluster stability and scalability and prevent overload during cluster join operations.
HiveMQ Enterprise Security Extension
- Updated the ESE Helper tool to 1.5.0 and replaced the various binary files with a JAR file and wrapper script.
HiveMQ Enterprise Extension for MySQL
- Fixed a rare issue where PUBLISH messages could be dropped if the database connection breaks.
- Fixed an issue where some PUBLISH messages were not consumed until the broker was restarted after the extension was disabled and re-enabled.
HiveMQ Enterprise Extension for MongoDB
- Fixed an issue where some PUBLISH messages were not consumed until the broker was restarted after the extension was disabled and re-enabled.
HiveMQ Enterprise Extension for PostgreSQL
- Fixed an issue where some PUBLISH messages were not consumed until the broker was restarted after the extension was disabled and re-enabled.
NOTE: Starting with HiveMQ 4.28, Java 21 is required to run the HiveMQ Platform.
If you use the official HiveMQ container images, no action is required – these images have shipped with Java 21 since HiveMQ 4.28.
Have a great day, The HiveMQ Team
HiveMQ Team
Team HiveMQ shares deep expertise in MQTT, Industrial AI, IoT data streaming, Unified Namespace (UNS), and Industrial IoT protocols. Our blogs explore real-world challenges, practical deployment guidance, and best practices for building modern, reliable, and a secure data backbone on the HiveMQ platform, along with thought leadership shaping the future of the connected world.
We’re on a mission to build the Industrial AI Platform that transforms industrial data into real-time intelligence, actionable insights, and measurable business outcomes.
Our experts are here to support your journey. Have questions? We’re happy to help. Contact us.
