rabbitmq-server 3.9.27-0ubuntu0.1 source package in Ubuntu

Changelog

rabbitmq-server (3.9.27-0ubuntu0.1) jammy; urgency=medium

  * New upstream version 3.9.27 (LP: #2060248):
    - In environments where DNS resolution is not yet available at the time
      RabbitMQ nodes boot and try to perform peer discovery, such as CoreDNS
      with default caching interval of 30s on Kubernetes, nodes now will
      retry hostname resolution (including of their own host) several times
      with a wait interval.
    - LDAP server password could end up in the logs in certain types of
      exceptions.
    - Details about these and many futher changes can be found at
      https://github.com/rabbitmq/rabbitmq-server/blob/main/release-notes/3.9.27.md
      and earlier versions in the same folder.
  * Added new dep8 tests (LP: #1679386):
    - d/t/hello-world
    - d/t/publish-subscribe
    - d/t/rpc
    - d/t/work-queue
  * Packaging changes needed by this update:
    - d/watch: update to find upstream tarball, and verify its signature.
    - d/upstream/signing-key.asc: added, downloaded from
      https://github.com/rabbitmq/signing-keys/releases/download/3.0/rabbitmq-release-signing-key.asc
    - Remove patches fixed upstream:
      - d/p/lp1999816-fix-rabbitmqctl-status-disk-free-timeout.patch.
    - d/p/CVE-2023-46118-{1,2}.patch: fix fuzz.
    - d/p/lets-use-python3-not-python-binary.patch: refresh.
    - d/p/downgrade_elixir.patch: downgrade the allowed elixir version minimum
      to 1.12.2 to allow Jammy to run. Upstream upgrades the minimum for general
      compiler optimizations, but is too recent for us.
    - d/p/max-ports-compat.patch: before v3.9.23, the maximum number of
      concurrent client connections was set based on the kernel open file handle
      limit. In v3.9.23 the concurrent client connection limit was changed to
      the value of the ERL_MAX_PORTS environment variable, and defaults to 65536
      if the variable is not set. To not change the behavior in upgrades to this
      version, this patch sets ERL_MAX_PORTS to the kernel open file handle
      limit if the variable is not set already. If the variable is set,
      then it's left alone. Note that ERL_MAX_PORTS must never be higher than
      the kernel open file handle limit.
    - d/rabbitmq-server.service: add notice about ERL_MAX_PORTS variable.
  * d/p/0007-Correctly-decrease-global-counters-in-rabbit_channel.patch: Fix
    errors in rabbitmq_global_publishers and rabbitmq_global_consumers counters
    (LP: #2073932).

 -- Mitchell Dzurick <email address hidden>  Thu, 04 Apr 2024 12:54:06 -0700

Upload details

Uploaded by:
Mitchell Dzurick
Uploaded to:
Jammy
Original maintainer:
Ubuntu Developers
Architectures:
all
Section:
net
Urgency:
Medium Urgency

See full publishing history Publishing

Series Pocket Published Component Section
Jammy updates main net

Builds

Jammy: [FULLYBUILT] amd64

Downloads

File Size SHA-256 Checksum
rabbitmq-server_3.9.27.orig.tar.xz 3.4 MiB 5012164e20fe1f95c98afd86936c4d97ac2701da6d4f69f88116963730a594a3
rabbitmq-server_3.9.27.orig.tar.xz.asc 833 bytes 1a6e3fb01bc9afc96281b486dc9a8261626f3c1dc3a756117381dadce218bd3e
rabbitmq-server_3.9.27-0ubuntu0.1.debian.tar.xz 32.8 KiB 40247b352b21933d2efb61d663ad78384c626a5323c8c7d7ae8df67359b299c1
rabbitmq-server_3.9.27-0ubuntu0.1.dsc 3.0 KiB 7de6483933a58ce678a156e817c7e7c4e704c39c06513f848d65c4f2763c2966

View changes file

Binary packages built by this source

rabbitmq-server: AMQP server written in Erlang

 RabbitMQ is an implementation of AMQP, the emerging standard for high
 performance enterprise messaging. The RabbitMQ server is a robust and
 scalable implementation of an AMQP broker.