The next UH Message Broker upgrade will bring the following changes:
| Item | Previously | Changed to… | Comments |
|---|---|---|---|
| Software version | RabbitMQ 3.7.12 Erlang 21.2.6 | RabbitMQ 3.11.2 Erlang 25.1.1 | Going forward, RabbitMQ and Erlang will be updated to the most recent versions as part of our monthly patching. |
| SSL Certificate | 2048-bit cert | 4096-bit Subject Alternative Name (SAN) extension to support host name associated with our perceived IP address. Please update the Intermediate(s)/Root cert bundle as described in TLS and RabbitMQ Java Client | |
| TLS | Versions 1.1 and 1.2 only. No peer verification if your TLS client sends an optional client cert. Secure renegotiation allowed. | Versions 1.2 and 1.3 only. Peer verification performed if your TLS client sends an optional client cert. Secure renegotiation disabled. | |
| RabbitMQ Java Client | Java client 3.6.6 or higher | Although we expect older clients to work, we recommend that you upgrade to the latest client | You should add code to verify the server cert and check the hostname. See TLS and RabbitMQ Java Client |
| RabbitMQ Perl Client | AnyEvent::RabbitMQ v1.16 | AnyEvent::RabbitMQ v1.16 or latest version Must also patch Net::AMQP::Common and add this line after line 239: l => \&unpack_long_long_integer | |
Queues | Classic queues which are mirrored and synchronized across all 3 nodes unless the queue name begins with an underscore. | All queues will be converted to quorum queues. | You do not need to change anything in your application. More on quorum queues: https://www.rabbitmq.com/quorum-queues.html |
Timeline
TBD