HiveMQ 4.28.16 Maintenance Release

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

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

HiveMQ Enterprise MQTT Broker

• Fixed an issue that caused the backpressure-active-clients and backpressure-active-receive-buffer metrics to remain high after the clients that caused backpressure were disconnected.
• Fixed an issue that could prevent the proper removal of enqueued retained messages from the message queue of a subscriber when using the discard-oldest strategy.
• Increased the number of retained messages that can be enqueued when a large max-queue-size is configured.
• To avoid unnecessary memory usage, the broker now determines whether an MQTT packet exceeds the maximum allowed size before fully decoding the message payload.
• REST API calls to get detailed client information for a specific client now contain field disconnectedSince that contains the time when a client was disconnected from the broker. This only affects clients that have persistent (cleanStart = false) sessions on the broker and were disconnected and have not connected again.

HiveMQ Enterprise Data Lake Extension

• Fixed an issue to enable the use of IAM Roles for Service Accounts (IRSA) for secure AWS access.

IMPORTANT: Starting with the next LTS version, Java 21 will be required to run the HiveMQ Platform.

We also recommend using Java 21 to run the current LTS line of 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