HiveMQ 4.28.10 Maintenance Release

The HiveMQ team is pleased to announce the availability of HiveMQ 4.28.10.

This maintenance release for the 4.28 series includes the following improvements:

HiveMQ Enterprise MQTT Broker

• Fixed an issue that could cause some message queue metrics to erroneously include no longer queued messages.
• Improved the performance of brokers with many concurrent connections during topology changes.
• Improved the robustness and sensitivity of the CONNECT overload protection and client overload protection (throttling).
• Removed obsolete client overload protection metrics:
  • com.hivemq.overload-protection.credits.per-tick
  • com.hivemq.overload-protection.clients.average-credits
  • com.hivemq.overload-protection.credits.subtracted.publishes
  • com.hivemq.overload-protection.credits.subtracted.subscribes
  • com.hivemq.overload-protection.credits.subtracted.unsubscribes
• Removed the trace-level log statement that shows the triggered number of credits for enabled client throttling to avoid information redundancy.
• Fixed an issue in overload protection level calculations that could unnecessarily delay the transition between levels.
• Fixed an issue that could negatively impact client connect performance when a connect takeover occurs during the client's CONNECT packet handling.

IMPORTANT: Java 21 will soon be required to run the HiveMQ Platform.

Since the HiveMQ 4.28 release in April 2024, Java 21 is recommended to run the HiveMQ Platform. For all HiveMQ versions released after April 2025, Java 21 will be required.

If you use the official HiveMQ container images, no action is required because these images have shipped with Java 21 since HiveMQ 4.28. If you do not run HiveMQ as a container, or you build your own container image, we recommend updating to Java 21 before the April 2025 deadline.

Have a great day, The HiveMQ Team