...
| Item | Previously | Changed to… | Comments | |||||
|---|---|---|---|---|---|---|---|---|
| Software version | RabbitMQ 3.7.12 Erlang 21.2.6 | RabbitMQ 3.11.13 Erlang 25.3 | Going forward, RabbitMQ and Erlang will be updated to the most recent versions as part of our monthly patching. | |||||
| Test server | Host: esb-test2.its.hawaii.edu | Host: esb-test1.its.hawaii.edu | esb-test1.its.hawaii.edu has data copied from esb-test2.its.hawaii.edu during January 2023. | |||||
| Production server | Host: esb.hawaii.edu | Host name will remain the same, but the IP address will change. Firewall rules have been copied, and you should verify that your production application will be able to reach this new IP address at port 5671. See 'how to test the new broker' below. | ||||||
| SSL Certificate | 2048-bit cert | 4096-bit cert signed by a new intermediate CA Subject Alternative Name (SAN) extension to support host name associated with our perceived IP address. | ||||||
| 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 | For proper security, you should eventually add code to verify our server cert/trust chain and hostname. The Java client does not do this out of the box. See TLS and RabbitMQ Java Client If you are already doing this, please note that there is a new CA signing our server cert, although the root CA is the same so this should not be a problem. If you run into issues, you might need to install the intermediate(s)/root cert bundle as explained in 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 | Management interface (UI) | When viewing a queue, using "Get messages" with any of the requeue options puts the message(s) back in their original order. | Any of the requeue options put the messages back but at the end of the queue | This is likely a bugNo change | We decided not to migrate to quorum queues with this upgrade. The order of messages is changed when messages are requeued, and this is a problem for many applications. |
Timeline
- The upgrade will happen on July 916, 2023.
How to test the new broker
...