MQTT runs into an exception published by AMQP 0-9-1 publishers with an expiration property set #12707
-
Describe the bugMessages with expiration property cause mqtt plugin to crash Reproduction stepsSubscribe to an mqtt queue Expected behaviorThe message should be consumed normally
Additional contextNo response |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 5 replies
-
|
Problem found in versions 3.13.x to 4.0.3 |
Beta Was this translation helpful? Give feedback.
-
|
@rdsilio please use Discussions for questions and investigations. We need an executable way to reproduce, that is, publishing should come from a client library, not a browser/HTTP API client. |
Beta Was this translation helpful? Give feedback.
-
|
According to @mkuratczyk, with an upcoming version of |
Beta Was this translation helpful? Give feedback.
-
|
Available now, in 0.16 |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Hi, I see this has been solved for RabbitMQ 4.0.x and 4.1.x, but it hasn't been solved for 3.13.x, which has commercial support until dec 2029. We face this issue and we would really appreciate this hotfix being included in 3.13.x. I know community support for this version ended, but is there any chance this fix could be included in 3.13.x? Thanks |
Beta Was this translation helpful? Give feedback.
-
|
This is fixed in VMware Tanzu RabbitMQ @keycad please create an issue using official Broadcom support channels and we will make sure that this gets backported to open-source RabbitMQ |
Beta Was this translation helpful? Give feedback.
-
|
If you do not hold a commercial license, you can contact sales via the |
Beta Was this translation helpful? Give feedback.
-
|
I backported the fix to open source RabbitMQ. The fix will be available in 3.13.16. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you very much @ansd ! |
Beta Was this translation helpful? Give feedback.
#12710
#12708