RabbitMQ 3.8.13 has been released. RabbitMQ is an open source implementation of Advanced Message Queuing Protocol (AMQP), written in Erlang, which is known for its high performance, robustness, and scalability, so it also inherits these advantages.
Core server
Bug fix
- Nodes with unusually long names (such as 150 or more characters) may use the direct reply-to identifier they generate to overflow the message attribute length. Now, the generated value is almost completely decoupled from the length of the node name.
Manage plugins
Bug fix
- The Consumer utilisation indicator has been renamed to consumer capacity to more accurately reflect consumer usage. This metric represents the percentage of time that RabbitMQ attempts to deliver to the queue consumer. For queues without consumers, the metric now returns 0%. For attempts to accept all consumer deliveries, the indicator will be around 100% (the best).
AMQP 1.0 plug-in
Bug fix
- The plug-in may encounter an unhandled exception.
OAuth 2 AuthN/AuthZ backend
Enhanced function
-
Some settings of the plug-in are now exposed
rabbitmq.conf
and provide verification:auth_backends.1 = oauth2 auth_oauth2.resource_server_id = a_resource_server_id auth_oauth2.additional_scopes_key = a_custom_scope_key auth_oauth2.default_key = ID1 auth_oauth2.signing_keys.id1 = /path/to/signing.key1.pem auth_oauth2.signing_keys.id2 = /path/to/signing.key2 .pem
-
Now, you can use
advanced.config
therabbitmq_auth_backend_oauth2.key_config.jwks_url
key in to obtain a JWT token from the provided JWKS endpoint.
Dependency upgrade
lager
Upgrade to 3.8.2cuttlefish
Upgrade to 2.6.0credentials_obfuscation
Upgrade to 2.4.0observer_cli
Upgrade to 1.6.0
For more details, please view: https://github.com/rabbitmq/rabbitmq-server/releases/tag/v3.8.13