You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[Blue-Green Deployment migration from RabbitMQ 3.13.x](https://www.rabbitmq.com/blog/2025/07/29/latest-benefits-of-rmq-and-migrating-to-qq-along-the-way)
75
75
to 4.2.0 is now easier to automate thanks to a new set of commands provided by [`rabbitmqadmin` v2](https://www.rabbitmq.com/docs/management-cli).
76
76
77
-
### Incoming and Outgoing Message Interceptors for Native Protocols
77
+
### Incoming and Outgoing Message Interceptors for Native Protocols (AMQP 1.0, AMQP 0-9-1, MQTTv3, MQTTv5)
78
78
79
79
Incoming and outgoing messages can now be intercepted on the broker.
80
-
This works for AMQP 1.0, AMQP 0.9.1, and MQTT.
80
+
This works for AMQP 1.0, AMQP 0.9.1, MQTTv3, and MQTTv5.
81
81
82
82
What the interceptor does is entirely up to its implementation, for example it can validate message metadata, add annotations, or perform arbitrary side effects.
83
83
Custom interceptors can be developed and integrated via [plugins](https://www.rabbitmq.com/docs/next/plugins).
@@ -220,6 +220,25 @@ This section is **incomplete** and will be expanded as 4.2 approaches its releas
220
220
221
221
#### Bug Fixes
222
222
223
+
* Classic queues could run into a rare message store exception that resuulted in
224
+
a loss of a few messages.
225
+
226
+
Special kudos to the contributors who have spent a very significant amount of time
227
+
reproducing and debugging the issue: @lhoguin@lukebakken@trvrnrth@gomoripeti
0 commit comments