Queens Series Release Notes

5.35.5

Known Issues

  • A bug in the amqp python library can cause the connection to the RabbitMQ broker to hang when using SSL/TLS. This results in frequent errors such as this:

    MessagingTimeout: Timed out waiting for a reply to message ID ae039d1695984addbfaaef032ce4fda3

    (see bug 1800957).

    This bug has been fixed in v2.4.1 of amqp.

    It is recommended that deployments using SSL/TLS upgrade the amqp library to v2.4.1 or later.

5.34.1

Other Notes

  • On RabbitMQ, in the past, acknowledgement of messages was done within the application callback thread/greenlet. This thread was blocked until the message was acknowledged. In Newton, we rewrote the message acknowledgement to ensure we haven’t two threads writing to the socket at the same time. Now all pending acknowledgements are done by the main thread. They are no more reason to block the application callback thread until the message is acknowledged. Other drivers already release the application callback threads before the message is acknowledged. This is also the case for RabbitMQ now.

5.33.0

Upgrade Notes

  • Change the default value of RPC dispatcher access_policy to DefaultRPCAccessPolicy.