November 19th, 2012· 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.
September 28th, 2012· Bugfixes to the broker, Erlang client, STOMP plugin, and management plugin.
August 23rd, 2012· A bugfix release with corrections to the broker, an Erlang client, and a management plugin as well as the shovel and federation plugins.
August 3rd, 2012· This is primarily a bugfix release, with several improvements to HA queues.
March 20th, 2012· 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.
December 21st, 2011· This version includes fixes to queue recovery and high availability node recovery; fixes to the STOMP adapter; compatibility with the latest Erlang release R15B; and general performance and bugfixes.
November 14th, 2011· Features of this release include: order preservation of re-queued messages; plugins included with the server download; "amqp" URI scheme for client connections; and performance improvements and bug fixes.
September 13th, 2011· 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.
September 2nd, 2011· 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 bugfixes.
June 17th, 2011· 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')
April 8th, 2011· This version fixes a number of bugs.
· In particular, it fixes a bug in 2.4.0 that would break upgrades if durable queues were present.
· A notable enhancement included in this release is cluster upgrades.
March 31st, 2011· This release fixes a number of bugs and introduces some enhancements, including fast routing for topic exchanges, sender-selected distribution and server-side consumer cancellation notifications.
February 8th, 2011· This release fixes a small number of bugs, in particular one serious bug in 2.3.0 which could lead to queue processes crashing.
December 1st, 2010· This version fixes a number of bugs and introduces some enhancements, including automatic upgrades of non-clustered brokers, per-queue message TTLs, and significantly reduced memory usage for pending acknowledgements.
October 20th, 2010· This version fixes a number of bugs and introduces some enhancements, including exchange to exchange bindings and some performance improvements in the server and clients.
September 16th, 2010· This version fixes a number of bugs, including some race conditions and introduces minor enhancements in the server and clients.
August 27th, 2010· This release includes a rewritten message store that pages messages to disk to relieve memory pressure, and support for AMQP 0-9-1. There are many other more modest additions, such as an implementation of basic.reject, and queue leases.
July 15th, 2010· This version of RabbitMQ can now be compiled with Erlang R14A. This is expected to bring relief for MacPorts users and Debian (unstable) users who build from source. Administration tools are now easier to use on MacPorts.
· Further enhancements include the ability to observe channel.flow events from the Java API and clustering usability improvements.
June 17th, 2010· This release introduces several APIs to extend Rabbit in a pluggable way, first with pluggable exchange types, and then with pluggable backing queues. Other improvements include optimisations for cross-node routing within a cluster, and more rigorous enforcement of channel.flow to ensure that Rabbit can stop producers who are failing to obey the instruction to stop sending messages to Rabbit when Rabbit comes under memory pressure.
February 16th, 2010· This release fixes yet more bugs specific to Windows in regards to memory monitoring, and works around various bat inadequacies. Other fixes include enforcing codec size limits, and handling some corner cases of basic.qos.
· The rabbitmqctl tool has been extended with several new commands. There have also been enhancements to the plugin system, and network performance over high-latency links. The exception reporting in the Java client has been improved and there are several bug fixes and enhancements to the AMQP Tracer tool.
June 18th, 2009· This release has 'beta' status and introduces a number of new features, such as prefetch count limiting, headers exchanges, fine-grained access control, and alternate exchanges. There are also improvements to performance and stability under high load, improved compatibility with other software (such as ejabberd and PowerShell), and a number of small bug fixes.
April 6th, 2009bug fixes:
· starting a RabbitMQ instance that contains a large number (thousands) durable exchanges, queues or bindings now takes just a few seconds instead of several minutes.
· on Windows, rabbitmq-multi.bat can now start RabbitMQ even when the path to the startup script contains spaces, whereas previously that would fail.
· on Windows, the rabbitmqctl.bat and rabbitmq-multi.bat scripts now report errors correctly instead of swallowing them.
enhancements:
· make the default settings of the various env vars which can be set in rabbitmq.conf visible to that script, thus permitting more advanced manipulation of the settings than was previously possible.
· permit configuration of rabbitmqctl's Erlang start parameters by sourcing rabbitmq.conf from the script and adding some env vars.
· on Windows, rabbitmq-server.bat and rabbitmq-multi.bat can now be configured with the RABBITMQ_{SERVER,MULTI}_{ERL,START}_ARGS env vars.
February 24th, 2009· This release has 'final' status and fixes a number of bugs in the server, the Java client, the .NET client, and the Debian/RPM packaging.
January 21st, 2009· This release fixes a number of bugs in the server, the .NET client, and the Debian/RPM packaging.
December 20th, 2008· This release contains a number of new features, as well as some bugfixes.
· The highlights are: removal of tickets and realms, implementation of 'queue.unbind', producer throttling when running low on memory, improved scalability of queue and binding creation and deletion, disabling of Nagle for more consistent latency, the addition of several management/info commands to rabbitmqctl, bugfixes in the area of connection and channel closure, support for the latest Erlang/OTP release (R12B-5), and improved configurability via environment variables.
Find us on Google+
