The HiveMQ team is pleased to announce the availability of HiveMQ 4.28.32.
This maintenance release for the 4.28 series includes the following bug fixes and improvements:
HiveMQ Enterprise MQTT Broker
- Updated the default
logback.xmlfile to write event logs asynchronously to avoid reduced broker performance when many clients connect and disconnect frequently. If you customized yourconf/logback.xmlfile, add the new asynchronous event log configuration manually during the upgrade. - Fixed an issue where a cluster could stop accepting new or rejoining nodes if a node left the cluster during a join operation or if data replication failed.
- Fixed an issue where a malformed CONNECT packet could abort active trace recordings.
- Fixed an issue where, under TCP backpressure, the broker could send MQTT packets such as PINGRESP after it sent a
DISCONNECTpacket for a keep-alive timeout. - Fixed an issue where extension consumers with overlapping topic filters could receive duplicate messages, which affected the Kafka, MongoDB, MySQL, PostgreSQL, Microsoft SQL Server, Data Lake, Snowflake, and Bridge extensions.
HiveMQ Enterprise Security Extension
- Fixed an issue where a MySQL realm that uses MySQL Connector/J could not connect over TLS when its configuration listed more than one TLS protocol or cipher suite.
HiveMQ Enterprise Extension for Kafka
- Fixed intermittent load failures of custom transformers with multiple constructors in the Kafka extension by always using the public no-argument constructor.
Have a great day, The HiveMQ Team