4fe4034b70
- Update to 4.1.5 * Highlights Khepri, an alternative schema data store developed to replace Mnesia, has matured and is now fully supported (it previously was an experimental feature) AMQP 1.0 is now a core protocol that is always enabled. Its plugin is now a no-op that only exists to simplify upgrades. The AMQP 1.0 implementation is now significantly more efficient: its peak throughput is more than double than that of 3.13.x on some workloads Efficient sub-linear quorum queue recovery on node startup using checkpoints Quorum queues now support priorities (but not exactly the same way as classic queues) AMQP 1.0 clients now can manage topologies similarly to how AMQP 0-9-1 clients do it The AMQP 1.0 convention (address format) used for interacting with with AMQP 0-9-1 entities is now easier to reason about Mirroring (replication) of classic queues was removed after several years of deprecation. For replicated messaging data types, use quorum queues and/or streams. Non-replicated classic queues remain and their development continues Classic queue storage efficiency improvements, in particular recovery time and storage of multi-MiB messages Nodes with multiple enabled plugins and little on disk data to recover now start up to 20-30% faster New exchange type: Local Random Exchange Quorum queue log reads are now offloaded to channels (sessions, connections). Initial Support for AMQP 1.0 Filter Expressions Feature Flags Quality of Life Improvements rabbitmqadmin v2 * Breaking Changes Before a client connection can negotiate a maximum frame size (frame_max), it must authenticate successfully. Before the authenticated phase, a special lower frame_max value is used. With this release, the value was increased from the original 4096 bytes to 8192 to accommodate larger JWT tokens. amqplib is a popular client library that has been using a low frame_max default of 4096. Its users must upgrade to a compatible version (starting with 0.10.7) or explicitly use a higher frame_max. amqplib versions older than 0.10.7 will not be able to connect to RabbitMQ 4.1.0 and later versions due to the initial AMQP 0-9-1 maximum frame size increase covered above. The default MQTT Maximum Packet Size changed from 256 MiB to 16 MiB. The following rabbitmq.conf settings are unsupported: cluster_formation.etcd.ssl_options.fail_if_no_peer_cert cluster_formation.etcd.ssl_options.dh cluster_formation.etcd.ssl_options.dhfile Classic Queues is Now a Non-Replicated Queue Type Quorum Queues Now Have a Default Redelivery Limit Up to RabbitMQ 3.13, when an AMQP 0.9.1 client (re-)published a message to RabbitMQ, RabbitMQ interpreted the AMQP 0.9.1 x-death header in the published message's basic_message.content.properties.headers field. RabbitMQ 4.x will not interpret this x-death header anymore when clients (re-)publish a message. CQv1 Storage Implementation was Removed Settings cluster_formation.randomized_startup_delay_range.* were Removed Several Disk I/O-Related Metrics were Removed Default Maximum Message Size Reduced to 16 MiB RabbitMQ 3.13 rabbitmq.conf setting rabbitmq_amqp1_0.default_vhost is unsupported in RabbitMQ 4.0. RabbitMQ 3.13 rabbitmq.conf settings mqtt.default_user, mqtt.default_password, and amqp1_0.default_user are unsupported in RabbitMQ 4.0. Starting with Erlang 26, client side TLS peer certificate chain verification settings are enabled by default in most contexts: from federation links to shovels to TLS-enabled LDAP client connections. RabbitMQ Shovels will be able connect to a RabbitMQ 4.0 node via AMQP 1.0 only when the Shovel runs on a RabbitMQ node >= 3.13.7. * See https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.0.1 * and https://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.1.0 for more info * Removed the following patches fixed upstream - fix-CVE-2025-30219.patch - fix-CVE-2025-50200.patch - rabbitmq-server-allow-elixir-1.18.patch - Add feature-suse-reproducable-build.patch to help with repoducable builds. -----------------------------------------------------------------
Simon Lees2025-11-28 12:04:28 +00:00
68bf50f2be
Rebase reproducable patch
Simon Lees
2025-11-27 12:55:16 +10:30
2defbe407d
Fix version requires in spec
Simon Lees
2025-11-27 12:11:48 +10:30
f77242d459
Intergrate all various changes
Simon Lees
2025-11-27 12:05:53 +10:30
866ed37713
Update changes file for 4.1.5
Simon Lees
2025-11-06 14:58:43 +10:30
10c608f30f
Test build of 4.1.5
Simon Lees
2025-10-31 11:45:10 +10:30
94e72155ee
- RabbitMQ Node can log Basic Auth header from an HTTP request (bsc#1245105, CVE-2025-50200) * fix-CVE-2025-50200.patch - bad logrotate configuration allows potential escalation from rabbitmq to root, /var/log/rabbitmq ownership is now 750 (bsc#1246091) - Make build reproducable * feature-suse-reproducable-build.patch
Simon Lees2025-08-04 07:08:45 +00:00
08497b7673
Accepting request 1286573 from home:simotek:branches:network:messaging:amqp
Simon Lees2025-06-18 08:08:01 +00:00
529d7d02c2
Accepting request 1272280 from network:messaging:amqp
Ana Guerrero2025-04-24 15:25:49 +00:00
79c18db752
- Force non parallel build, this has been the cause of some intermittent build failures.
Simon Lees2025-04-24 03:05:12 +00:00
22b5c78d46
Accepting request 1247250 from network:messaging:amqp
Ana Guerrero2025-02-20 15:40:26 +00:00
ea62fe0c09
- Add rabbitmq-server-allow-elixir-1.18.patch: Allow building CLI with elixir 1.18.x. Based on upstream commit 5086e283.
Simon Lees2025-02-20 01:21:43 +00:00
03a9bbb96f
Accepting request 1200873 from network:messaging:amqp
Ana Guerrero2024-09-15 10:36:20 +00:00
4d222a2174
- update to 3.12.11: * Quorum queue declared when one of cluster nodes was down could trigger connection exceptions. * Avoids a rare exception that could stop TCP socket writes on a client connection. * queue_deleted and queue_created internal events now include queue type as a module name, and not an inconsistent (with the other queue and stream types) value classic. * Definition files that are virtual host-specific cannot be imported on boot. Such files will now be detected early and the import process will terminate after logging a more informative message. * Several AMQP 1.0 application properties are now more correctly converted to AMQP 0-9-1 headers by cross-protocol Shovels. * The priority property now populates an AMQP 1.0 header with the same name, per AMQP 1.0 spec. * Metric label values now escape certain non-ASCII characters. * Avoids an exception when an MQTT client that used a QoS 0 subscription reconnects and its original connection node is down. * Avoids an exception when an MQTT client connection was force- closed via the HTTP API. * Certain CLI commands could not be run in a shell script loop, unless the script explicitly redirected standard input. * rabbitmq-diagnostics cluster_status now responds much quicker when a cluster node has gone down, were shut down, or otherwise has become unreachable by the rest of the cluster. * Reverted a change to DELETE /api/queues/{vhost}/{name} that allowed removal of exclusive queues and introduced
Dirk Mueller2024-01-06 13:22:16 +00:00
ed3634dd1d
Accepting request 1133729 from network:messaging:amqp
Ana Guerrero2023-12-17 20:34:11 +00:00
b9e380e8d8
- update to 3.12.10: * Avoids two Shovels being started after an upgrade from 3.12.6 or older versions. * When a topic permission was deleted, an internal event of type permission.deleted was emitted in some cases, instead of topic.permission.deleted. * Shovels on 3.12.8 nodes failed during a rolling cluster upgrade due to internal identifier format changes. * Avoids an unnecessary warning in the logs. * avoids a potential exception in the autoheal partition handler. * raft.segment_max_entries is now validated to prevent the value from overflowing its 16-bit segment file field. Maximum supported value is now 65535.
Dirk Mueller2023-12-17 10:01:58 +00:00
2754d36f62
Accepting request 1121010 from network:messaging:amqp
Ana Guerrero2023-10-29 18:42:06 +00:00
877a559315
- update to 3.12.7: * Stream replication connections configured to use exclusively TLSv1.3 failed. * On startup, stream replicas will handle one more potential case of segment file corruption after an unclean shutdown. * default_policies.*.queue_pattern definition in rabbitmq.conf was incorrectly parsed. * Avoid log noise when inter-node connections frequently fail and recover. * Optimized stream index scans. Longer scans could result in some replicas stopping with a timeout. * Classic queue storage version is now a supported key for operator policies. * Queue length limit overflow behavior now can be configured via operator policies. * Several list_stream_* commands (available via both rabbitmq-diagnostics and rabbitmq-streams) commands now can display replica node in addition to other fields. * rabbitmqctl add_user now can accept a pre-generated salted password instead of a plain text password, both as a positional argument and via standard input: * Message consumption with the "Nack message, requeue: true" option did not actually requeue deliveries. * HTTP API request body size is now limited to 10 MiB by default. * Two endpoints, one that accepts messages for publishing (note: publishing over the HTTP API is greatly discouraged) * and another for definition import, * will now reject larger transfers with a 400 Bad Request response.
Dirk Mueller2023-10-29 15:44:11 +00:00
88c1b022d0
Accepting request 1099488 from network:messaging:amqp
Ana Guerrero2023-07-19 17:11:44 +00:00
653cf908b1
Accepting request 1099317 from home:matwey:branches:network:messaging:amqp
Dirk Mueller2023-07-19 11:12:25 +00:00
Dominique Leuenberger
Fridrich Strba
Simon Lees
Simon Lees
Ana Guerrero
Dirk Mueller
Fusion Future
Peter Simons
Gabriele Santomaggio