RabbitMQ

RabbitMQ is made up of two parts. A server that tells messages where to go and client for sending and receiving data.

Working around AMQP (Advanced Message Queuing Protocol ), RabbitMQ is designed to efficiently support a wide variety of messaging applications and communication patterns, helping developers create (Web-)software that communicates with a server or with its component parts.

Besides the special server used for these operations, RabbitMQ currently offers official and unofficial clients for:

PHP

Perl

What is new in this release:

• Priority queues
• Faster persistence
• I/O statistics
• .NET client API changes

What is new in version 3.6.0:

• Priority queues
• Faster persistence
• I/O statistics
• .NET client API changes

What is new in version 3.5.5:

• Priority queues
• Faster persistence
• I/O statistics
• .NET client API changes

What is new in version 3.5.3:

• Priority queues
• Faster persistence
• I/O statistics
• .NET client API changes

What is new in version 3.5.1:

• Priority queues
• Faster persistence
• I/O statistics
• .NET client API changes

What is new in version 3.4.4:

• Fast RPC replies
• Live plugin activation
• Reconnecting .NET client

What is new in version 3.3.5:

• Provide a mechanism for diagnosing stuck processes
• Correctly read /proc/meminfo on Linux even if rows do not contain colons
• Added loopback_users to the sample configuration file
• Prevent long delays in publishing after a node goes down and network connections to it time out
• Provide unminimised versions of all bundled JavaScript libraries

What is new in version 3.3.0:

• Dynamic shovels
• Reconnecting Java client
• Consumer prefetch

What is new in version 3.2.0:

• Federated queues
• Enhanced policies
• Consumer priorities
• Blocked connection notifications
• Authentication failure notifications

What is new in version 3.1.4:

• This release fixes two security bugs: a directory traversal bug for the management plugin (and other HTTP applications) on Windows, and a means to subvert publish access control using dead-lettering.

What is new in version 3.1.2:

• Bug fixes.

What is new in version 3.1.1:

• Bug fixes.

What is new in version 3.1.0:

• Eager synchronization of mirror queue slaves
• Automatic cluster partition healing
• Charts in the management plugin
• Queue length limits

What is new in version 3.0.2:

• This release fixes a number of bugs in 3.0.1 and earlier versions.

What is new in version 3.0.0:

• This release introduces dynamic, policy-based control of mirroring and federation, improves the user friendliness of clustering, adds support for per-message TTL, introduces plugins for web-STOMP and MQTT, and adds many smaller new features and bug fixes.

What is new in version 2.8.7:

• This release fixes a number of bugs in the broker, Erlang client and STOMP and management plugins.

What is new in version 2.8.5:

• This is primarily a bugfix release, with several improvements to HA queues.

What is new in version 2.8.4:

• Fixed bug which can cause log rotation to trigger a state where the log file grows rapidly and without end, eventually exhausting all available disk space.

What is new in version 2.8.3:

• This is primarily a bugfix release, with some minor enhancements (make disk space monitoring less intrusive by default, improve SSL performance with the Java client).

What is new in version 2.8.2:

• This release fixes a number of bugs and improves performance in a variety of areas, as well as introducing disc space monitoring and federation status reporting.

What is new in version 2.8.0:

• This release fixes a number of bugs and adds new features. Notable new features include:
• Dead lettering - queues can specify an exchange to which messages should be redirected when they are rejected or expire.
• Internal flow control to limit memory use and make performance more predictable if the server is overloaded.

What is new in version 2.7.1:

• This release includes important fixes to high availability recovery, fixes to the STOMP adapter, compatibility with Erlang Release R15B, and general improvements to the management interface, performance and stability.

What is new in version 2.6.1:

• This release fixes a bug in the 2.6.0 version that causes the broker to fail to restart on reboot on some operating systems.

What is new in version 2.6.0:

• The highlight of this release is the introduction of active-active HA, with queues getting replicated across nodes in a cluster. There are many other improvements, particularly to the management and stomp plug-ins, as well as a number of bug fixes.

What is new in version 2.5.1:

• This release correctly upgrades from RabbitMQ 2.1.1 and 2.2.0. There are no other changes compared with 2.5.0.

What is new in version 2.5.0:

• Changes:
• Recovery has been simplified, improving startup times when many exchanges or bindings exist.
• Bindings are recovered between durable queues and non-durable exchanges on restart of individual cluster nodes.
• Better performance under high load and memory pressure.
• Source compatibility with the new Erlang R14B03 release.
• New features include:
• Tracing facility for debugging incoming and outgoing messages, (see firehose).
• Improved inbound network performance.
• Improved routing performance.
• New rabbitmqctl commands ('report', 'environment', and 'cluster_status').

What is new in version 2.4.1:

• Bug fixes:
• Fix breakage of upgrades when durable queues are present or following a non-clean shutdown.
• Prevent "rabbitmqctl wait" from waiting forever in certain circumstances.
• The broker can be run on Erlang R12B-3 again.
• Some other small bug fixes.
• Enhancements:
• Upgrades in clusters.
• Improve memory usage when dealing with persistent messages waiting on acks from consumers.
• Better error reporting for some startup problems.
• Add timestamp to events published to the amq.rabbit.log exchange.

What is new in version 2.4.0:

• Bug fixes:
• In a cluster, don't fail with an internal-error when re-declaring a queue on a connection to a node other than the queue's "home" node.
• In a cluster, report a not-found error instead of internal-error when attempting to re-declare a durable queue whose node is unavailable.
• Do not ignore the RABBITMQ_LOG_BASE variable on Windows.
• Fix a bug causing SSL connections to die on Erlang prior to R14 when using "rabbitmqctl list_connections" with the SSL options.
• Various minor fixes.
• Enhancements:
• Greatly speed up routing for topic exchanges with many bindings.
• Propagate memory alarms across cluster, thus reacting better to memory pressure on individual nodes.
• Sender-selected distribution (i.e. add support for the CC and BCC headers).

What is new in version 2.3.0:

• This release fixes a number of bugs and introduces some enhancements, including streaming publish confirmations, new plugin mechanisms for authentication and authorisation, and a great deal more.

What is new in version 2.2.0:

• Bug fixes:
• Fix issue that causes cross-cluster communication to deadlock after sustained cluster activity.
• Fix queue memory leak when using the management plugin or other consumers of queue statistics.
• Brokers started with rabbitmq_multi.bat are now restartable.
• Clustering reset no longer destroys installed plugins.
• Fix race condition between queue declaration and connection termination that causes spurious noproc errors to appear in the log.
• Fix memory leak when long-running channels consume and cancel on many queues.
• queue.declare and exchange.declare raise precondition_failed rather than not_allowed when attempting to redeclare a queue or exchange with parameters different than those currently known to the broker.

What is new in version 2.1.1:

• This release fixes a number of bugs and introduces some enhancements, including exchange to exchange bindings and some performance improvements, in the server and clients.