Also keep an eye on the How To page, which is constantly updated with links to relevant community tools and documentation.
The RabbitMQ team is pleased to announce the release of RabbitMQ 3.1.1.
This is primarilly a bug fix release.
Binary and source distributions of the new release can be found on the download page.
We encourage all users of earlier versions of RabbitMQ to upgrade to this latest release.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us on the RabbitMQ discussion list (signup here and then e-mail to <rabbitmq-discuss at lists.rabbitmq.com>).
RabbitMQ v3.1.0 is significant because it introduces an important set of new features, making Rabbit easier to use and manage.
V3.1.0 has significance for another reason: it is the first release made under the banner of our new sponsor company, Pivotal. Pivotal launched earlier this year as a joint venture between VMware, EMC and with a strategic partnership with General Electric Global Software. Billed as "A New Platform for a New Era", the Pivotal platform will unite data, application, and cloud fabrics. The Rabbit team members are excited to be part of this bold new initiative driving open source innovation and collaboration.
RabbitMQ will continue to be available under the open source Mozilla Public License or commercial terms. Commercial support, consulting and both self-paced and instructor-led training courses are still available worldwide. The rabbitmq-discuss mailing list will continue to be the primary channel of communication about open-source RabbitMQ. The release cycle is not expected to change as a result of the change of ownership.
We invite all customers to continue with us on the journey to become the most reliable, scalable and portable messaging system.
The RabbitMQ team is pleased to announce the release of RabbitMQ 3.1.0.
This release introduces eager synchronisation of mirror queue slaves, automatic cluster partition healing, and improved statistics (including charts) in the management plugin. It also adds many smaller new features, bug fixes and performance improvements.
Binary and source distributions of the new release can be found on the download page.
We encourage all users of earlier versions of RabbitMQ to upgrade to this latest release.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us on the RabbitMQ discussion list (signup here and then e-mail to <rabbitmq-discuss at lists.rabbitmq.com>).
The RabbitMQ team is pleased to announce the release of RabbitMQ 3.0.4.
This release fixes a bug in the federation plugin where upstream credentials were leaked in the x-received-from header. This bug had been in the federation plugin since RabbitMQ 3.0.0. There are no other changes from RabbitMQ 3.0.3.
Binary and source distributions of the new release can be found on the download page.
We encourage all users of earlier versions of RabbitMQ to upgrade to this latest release.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us on the RabbitMQ discussion list (signup here and then e-mail to <rabbitmq-discuss at lists.rabbitmq.com>).
The RabbitMQ team is pleased to announce the release of RabbitMQ 3.0.3.
This release fixes a small number of bugs in 3.0.2 and earlier versions.
Binary and source distributions of the new release can be found on the download page.
We encourage all users of earlier versions of RabbitMQ to upgrade to this latest release.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us on the RabbitMQ discussion list (signup here and then e-mail to <rabbitmq-discuss at lists.rabbitmq.com>).
The RabbitMQ team is pleased to announce the release of RabbitMQ 3.0.2.
This release fixes a number of bugs in 3.0.1 and earlier versions.
Binary and source distributions of the new release can be found on the download page.
We encourage all users of earlier versions of RabbitMQ to upgrade to this latest release.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us on the RabbitMQ discussion list (signup here and then e-mail to <rabbitmq-discuss at lists.rabbitmq.com>).
The RabbitMQ team is pleased to announce the release of RabbitMQ 3.0.1.
This release fixes a number of bugs in 3.0.0 and earlier versions.
Binary and source distributions of the new release can be found on the download page.
We encourage all users of earlier versions of RabbitMQ to upgrade to this latest release.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us on the RabbitMQ discussion list (signup here and then e-mail to <rabbitmq-discuss at lists.rabbitmq.com>).
The RabbitMQ team is pleased to announce the release of RabbitMQ 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.
Binary and source distributions of the new release can be found on the download page.
We encourage all users of earlier versions of RabbitMQ to upgrade to this latest release.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us on the RabbitMQ discussion list (signup here and then e-mail to <rabbitmq-discuss at lists.rabbitmq.com>).
The RabbitMQ team is delighted to announce the release of RabbitMQ 2.8.7.
This release fixes a number of bugs in the broker, Erlang client and STOMP and management plugins.
Binary and source distributions of the new release can be found on the download page.
We encourage all users of earlier versions of RabbitMQ to upgrade to this latest release.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us on the RabbitMQ discussion list (signup here and then e-mail to <rabbitmq-discuss at lists.rabbitmq.com>).
The RabbitMQ team is delighted to announce the release of RabbitMQ 2.8.6.
This release fixes a number of bugs, including one introduced in 2.8.5 that could cause an error during shutdown of mirrored queues.
Binary and source distributions of the new release can be found on the download page.
We encourage all users of earlier versions of RabbitMQ to upgrade to this latest release.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us on the RabbitMQ discussion list (signup here and then e-mail to <rabbitmq-discuss at lists.rabbitmq.com>).
The RabbitMQ team is pleased to announce the release of RabbitMQ 2.8.5.
This is primarily a bugfix release, with several improvements to HA queues.
The new release can be downloaded from the download page.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us on the RabbitMQ discussion list (signup here and then e-mail to <rabbitmq-discuss at lists.rabbitmq.com>).
We've found an unpleasant bug in RabbitMQ 2.8.3 which can cause log rotation to trigger a state where the log file grows rapidly and without end, eventually exhausting all available disk space.
If you are running RabbitMQ 2.8.3 you are strongly advised to upgrade to 2.8.4 immediately and in the meantime do not invoke "rabbitmqctl rotate_logs". This applies particularly strongly to users of the RPM and .deb packages, since these are configured to rotate logs automatically.
Other versions of RabbitMQ are not affected by this bug.
Binary and source distributions of the new release can be found on the download page.
We encourage all users of earlier versions of RabbitMQ to upgrade to this latest release.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us on the RabbitMQ discussion list (signup here and then e-mail to <rabbitmq-discuss at lists.rabbitmq.com>).
The RabbitMQ team is pleased to announce the release of RabbitMQ 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).
Binary and source distributions of the new release can be found on the download page.
We encourage all users of earlier versions of RabbitMQ to upgrade to this latest release.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us on the RabbitMQ discussion list (signup here and then e-mail to <rabbitmq-discuss at lists.rabbitmq.com>).
The RabbitMQ team is pleased to announce the release of RabbitMQ 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.
Binary and source distributions of the new release can be found on the download page.
We encourage all users of earlier versions of RabbitMQ to upgrade to this latest release.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us on the RabbitMQ discussion list (signup here and then e-mail to <rabbitmq-discuss at lists.rabbitmq.com>).
The RabbitMQ team is pleased to announce the release of RabbitMQ 2.8.1.
This release fixes a small number of bugs, including one which prevented cluster RAM nodes which had run an earlier version from being upgraded.
Binary and source distributions of the new release can be found on the download page.
We encourage all users of earlier versions of RabbitMQ to upgrade to this latest release.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us on the RabbitMQ discussion list (signup here and then e-mail to <rabbitmq-discuss at lists.rabbitmq.com>).
The RabbitMQ team is pleased to announce the release of RabbitMQ 2.8.0.
This release fixes a number of bugs and adds new features. Notable new features include:
Binary and source distributions of the new release can be found on the download page.
We encourage all users of earlier versions of RabbitMQ to upgrade to this latest release.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us on the RabbitMQ discussion list (signup here and then e-mail to <rabbitmq-discuss at lists.rabbitmq.com>).
The RabbitMQ team is delighted to announce the release of RabbitMQ 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.
Binary and source distributions of the new release can be found on the download page.
We encourage all users of earlier versions of RabbitMQ to upgrade to this latest release.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us on the RabbitMQ discussion list (signup here and then e-mail to <rabbitmq-discuss at lists.rabbitmq.com>), or contact us directly by e-mailing <info at rabbitmq.com>.
The RabbitMQ team is delighted to announce the release of RabbitMQ 2.7.0.
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.
Binary and source distributions of the new release can be found on the download page.
We encourage all users of earlier versions of RabbitMQ to upgrade to this latest release.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us on the RabbitMQ discussion list (signup here and then e-mail to rabbitmq-discuss at lists.rabbitmq.com), or contact us directly by e-mailing to info at rabbitmq.com.
The RabbitMQ team is pleased to announce the release of RabbitMQ 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.
Binary and source distributions of the new release can be found in the usual place.
We recommend that all users of earlier versions of RabbitMQ upgrade to this latest release.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us via the RabbitMQ discussion list at rabbitmq-discuss@lists.rabbitmq.com, or directly at info@rabbitmq.com.
The RabbitMQ team is happy to announce that the RabbitMQ add-on for Heroku is now available in beta. You can read about it on on the Heroku blog and on the RabbitMQ blog. And there is more information and links to sample code on this page.
The RabbitMQ team is pleased to announce the release of RabbitMQ 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. See the release notes for more details.
Binary and source distributions of the new release can be found in the usual place.
We recommend that all users of earlier versions of RabbitMQ upgrade to this latest release.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us via the RabbitMQ discussion list at rabbitmq-discuss@lists.rabbitmq.com, or directly at info@rabbitmq.com.
The RabbitMQ team is excited to announce the launch of the RabbitMQ service on CloudFoundry.com. This service brings the messaging functionality of RabbitMQ to developers building applications on Cloud Foundry. Please see the main announcement over on the Cloud Foundry blog. There's also an FAQ with more details on the Cloud Foundry knowledge base.
The RabbitMQ team is pleased to announce the release of RabbitMQ 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.
For details see the release notes.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us via the RabbitMQ discussion list, or directly at info@rabbitmq.com.
The RabbitMQ team is delighted to announce the release of RabbitMQ 2.5.0.
This release fixes a number of bugs. In particular:
For details see the release notes.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us via the RabbitMQ discussion list, or directly at info@rabbitmq.com.
The RabbitMQ team is delighted to announce the release of RabbitMQ 2.4.1.
This release fixes a number of bugs, in particular one bug in 2.4.0 that would break upgrades if durable queues were present. A notable enhancement included in this release are cluster upgrades. For details see the release notes.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us via the RabbitMQ discussion list, or directly at info@rabbitmq.com.
Alvaro Videla, co-author of RabbitMQ in Action, will be speaking about RabbitMQ and messaging patterns at the next Erlang Factory meeting in London, June 9-10th.
Alvaro will present how to implement several messaging patterns using RabbitMQ such as:
To learn more, visit the Erlang Factory website.
The RabbitMQ team and SpringSource are pleased to announce that the Spring AMQP Project (for Java) has reached RC1 status.
For details see the release notes.
You can download the distribution zip file. The JARs are available in the SpringSource Milestone Maven repository.
To learn more about the project and provide welcome feedback, please visit the Spring AMQP homepage for links to downloads, documentation, the forum and more.
The RabbitMQ team is delighted to announce the release of RabbitMQ 2.4.0.
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. For details see the release notes.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us via the RabbitMQ discussion list, or directly at info@rabbitmq.com.
The RabbitMQ team is pleased to announce the release of RabbitMQ 2.3.1.
This release fixes a small number of bugs, in particular one serious bug in 2.3.0 which could lead to queue processes crashing. For details see the release notes.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us via the RabbitMQ discussion list, or directly at info@rabbitmq.com.
Perfectly timed one day before the start of the year of the Rabbit, the RabbitMQ team is pleased to announce the release of RabbitMQ 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. For details see the release notes.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us via the RabbitMQ discussion list, or directly at info@rabbitmq.com.
A recording of the webinar is available.
We are pleased to announce that we will be hosting our first, live (and free) webinar today at 1500 GMT and repeated at 1300 EST / 1000 PST.
Emile, from the RabbitMQ engineering team, will look at the relevance of Erlang/OTP as an implementation platform, the benefits of a messaging system and common messaging patterns. Some important features in recent releases will be discussed with examples. Join us to find out how RabbitMQ can help to scale your application, whether it's on a device, the web, in the data centre, or the cloud.
To register, please visit the SpringSource events page.
The RabbitMQ team is pleased to announce the release of RabbitMQ 2.2.0.
This release 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. For details see the release notes.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us via the RabbitMQ discussion list, or directly at info@rabbitmq.com.
The RabbitMQ team is pleased to announce the release of RabbitMQ 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.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us via the RabbitMQ discussion list, or directly at info@rabbitmq.com.
The RabbitMQ team is pleased to announce the release of RabbitMQ 2.1.0.
This release fixes a number of bugs, including some race conditions and introduces minor enhancements in the server and clients.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us via the RabbitMQ discussion list, or directly at info@rabbitmq.com.
We the RabbitMQ team are delighted to announce the release of RabbitMQ 2.0.0.
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. For details see the release notes.
Binary and source distributions of the new release can be found in the usual place.
This now includes binary packages of plugins. Please note the caveats there.
We recommend that all users of earlier versions of RabbitMQ upgrade to this latest release.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us via the RabbitMQ discussion list, or directly at info@rabbitmq.com.
The RabbitMQ team and SpringSource are pleased to announce the first milesone release of the Spring AMQP Project 1.0 M1.
Spring AMQP makes common Spring idoms available to developers who are building AMQP-based messaging solutions. For example, building a messaging application that uses RabbitMQ as broker will feel quite similar to building an application based on Spring's JMS support. The project consists of both Java and .NET versions.
To learn more about the project, visit the Spring AMQP homepage for links to downloads, documentation, the forum and more.
The RabbitMQ team is pleased to announce the release of RabbitMQ 1.8.1.
This release 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.
For details see the release notes.
Binary and source distributions of the new release can be found in the usual place.
We recommend that all users of earlier versions of RabbitMQ upgrade to this latest release.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us via the RabbitMQ discussion list at rabbitmq-discuss@lists.rabbitmq.com, or directly at info@rabbitmq.com.
The RabbitMQ team is pleased to announce the release of RabbitMQ 1.8.0.
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.
For details see the release notes.
Binary and source distributions of the new release can be found in the usual place.
We recommend that all users of earlier versions of RabbitMQ upgrade to this latest release.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us via the RabbitMQ discussion list at rabbitmq-discuss@lists.rabbitmq.com, or directly at info@rabbitmq.com.
Rabbit Technologies Ltd. (RTL), the company behind RabbitMQ, today announced that the company is to be acquired by SpringSource, a division of VMware, Inc.. RTL was founded in February 2007 and is a spin out from LShift Ltd., the UK software consultancy, and Cohesive FT, the US virtualization and cloud computing company.
The Rabbit Team are very excited about the deal. “RabbitMQ is an extremely successful technology and forms the backbone for many varied cloud messaging systems,” said Alexis Richardson, chief executive officer and co-founder, Rabbit Technologies, Ltd. “By providing a multi-protocol, completely open, portable messaging system, our technology can be a key enabler of tomorrow’s applications. By joining with enterprise leaders, SpringSource and VMware, RabbitMQ expects to continue to be at the forefront of the movement toward cloud computing. Users and customers will benefit from an organization offering deep and immediate experience with the challenges of managing highly available and stable operations.”
RabbitMQ will continue to be open source and distributed in the same way as before. The RabbitMQ community can expect to see increased investment in this outstanding technology which should result in significant improvements to the open source release.
RabbitMQ customers will see an increase in availability of training, professional services and support offerings as the RabbitMQ business is integrated with SpringSource.
For more details please see the full press release.
Contacts:
SpringSource and VMware
Charlie Purdom, cpurdom@vmware.com
Ross Levanto or Christine McKeown, springsource@schwartz-pr.com
Rabbit Technologies Ltd.
Alexis Richardson, alexis@rabbitmq.com
LShift Ltd.
Mike Rowlands, press@lshift.net
Cohesive FT
Dwight Koop, dwight.koop@cohesiveft.com
Acknowledgements:
Rabbit Technologies would like to thank Orrick, Herrington & Sutcliffe LLP (London) for acting as counsel throughout the acquisition process. Visit their website.
Alexis Richardson, Rabbit Technologies CEO, will be speaking at the Cloud & Grid Exchange in London, 23rd April. In his talk, Alexis will present use cases for cloud messaging: what is messaging and why it is useful for cloud computing? This talk will answer these questions by way of illustrating use cases from RabbitMQ customers.
The RabbitMQ team is pleased to announce the release of RabbitMQ 1.7.2.
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.
For details see the release notes.
Binary and source distributions of the new release can be found in the usual place.
We recommend that all users of earlier versions of RabbitMQ upgrade to this latest release.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us via the RabbitMQ discussion list at rabbitmq-discuss@lists.rabbitmq.com, or directly at info@rabbitmq.com.
The RabbitMQ team is pleased to announce the release of RabbitMQ 1.7.1.
This release fixes a number of bugs specific to Windows, several problems in the ssl support and plug-in system, some race conditions and corner cases in the AMQP protocol and connection lifecycle handling, breakages in Debian and RPM package removal, as well as some minor bugs in rabbitmqctl.
There are also some noteworthy enhancements, such as the support for complete short node names in all the startup and control scripts (making it easier to install RabbitMQ on systems with changing host names), improved memory monitoring and producer throttling, an extension of the AMQP codec with array types, better support for MacPorts, and improved performance and error reporting in the Java and .Net clients.
For details see the release notes.
Binary and source distributions of the new release can be found in the usual place.
We recommend that all users of earlier versions of RabbitMQ upgrade to this latest release.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us via the RabbitMQ discussion list at rabbitmq-discuss@lists.rabbitmq.com, or directly at info@rabbitmq.com.
RabbitMQ was listed as one of the Best Cloud Application Providers in John M Willis second annual 'Cloudies' awards. John has worked in the IT management industry for 30 years and is known internationally for his IT Management and Cloud blog.
RabbitMQ 1.7.0 is now in Fedora 10, 11, and 12, and EPEL. So, for all Fedora users RabbitMQ is now just a
yum install rabbitmq-server away!
For the full package details see the Fedora Project website.
Rabbit Technologies Limited, the company behind RabbitMQ, today announced the signing of a formal teaming agreement with Ubuntu sponsor Canonical. The goal of the partnership is to promote open standards in the emerging cloud computing space.
"We want to be sure our users can navigate safely into the cloud", said Simon Wardley, software services manager for Canonical, "and we see this working according to three rules. Rule one is to build on their own infrastructure. Rule two is moving between their infrastructure and an external provider. Rule three is switching between providers. RabbitMQ provides an important message bus in the cloud that enables applications to interoperate without dependency upon a proprietary solution. It will play a significant role in the future of cloud switching."
For details see the full press release.
The RabbitMQ team is pleased to announce the release of RabbitMQ 1.7.0.
This release has 'beta' status and introduces a number of new features, such as native SSL support, a plugin mechanism, and a Windows installer for the .net client. There are also improvements to error reporting and diagnostics, performance and stability, the windows bundle (which now includes the .net client and a more recent version of Erlang/OTP), server installation and configuration. Finally, there are a number of small bug fixes.
For details see the release notes.
Binary and source distributions of the new release can be found in the usual place
We recommend that all users of earlier versions of RabbitMQ upgrade to this latest release.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us via the RabbitMQ discussion list at rabbitmq-discuss@lists.rabbitmq.com, or directly at info@rabbitmq.com.
We are delighted to be providing RabbitMQ open messaging to support the VMware vCloud Initiative, their customers and the growing cloud ecosystem," Alexis Richardson, CEO, RabbitMQ. "Customers want choice, and RabbitMQ delivers choice by lowering the cost of scale, and by removing lock-in. RabbitMQ is the market leading implementation of AMQP, the interoperable open business messaging protocol, and is distributed on most major development platforms. Already businesses are using RabbitMQ to scale up business-critical application functionality on multiple leading public and private cloud infrastructures. Our support for the VMware vCloud Initiative is a natural extension. RabbitMQ has an open source license making it ideal for elastic deployments, and for integration in platforms such as Spring and Ruby on Rails.
The virtual appliance is available to download for free from the VMware virtual appliance marketplace.
The RabbitMQ team have been busy giving presentations about the use of RabbitMQ at events like Google London, Oxford Geek Night, Erlang Factory etc. Many of these presentations were filmed, and you can catch up online.
Check out these bookmarks on Delicious.
There have also been many exciting developments in the RabbitMQ community recently. Keep an eye on this page for a summary of who is doing what, and how, with RabbitMQ.
Kaazing Corporation, makers of gateways that connect web-based applications to high-volume, real-time message traffic, today announced support for the Advanced Message Queuing Protocol (AMQP) in the most recent release of the company's flagship product, Kaazing Enterprise Gateway (KEG).
For details see the full release.
The RabbitMQ team is pleased to announce the release of RabbitMQ 1.6.0.
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.
For details see the release notes.
Binary and source distributions of the new release can be found in the usual place
We recommend that all users of earlier versions of RabbitMQ upgrade to this latest release.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us via the RabbitMQ discussion list at rabbitmq-discuss@lists.rabbitmq.com, or directly at info@rabbitmq.com.
RabbitMQ is now included in the Fedora Linux distribution. See fedoraproject.org for the package details.
So, for all Fedora users RabbitMQ is now just a
yum install rabbitmq-server away.
Thanks go to the Fedora community for their guidance in getting our RPM packages into shape for inclusion.
The RabbitMQ team is pleased to announce the release of RabbitMQ 1.5.5
This release has 'final' status and fixes a small number of bugs in the server, the startup and control scripts on Windows, and the Debian/RPM packaging. Also included are some minor enhancements to the way the server can be configured. The RabbitMQ clients have remained unchanged.
For details see the release notes.
Binary and source distributions of the new release can be found in the usual place
We recommend that all users of earlier versions of RabbitMQ upgrade to this latest release.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us via the RabbitMQ discussion list at rabbitmq-discuss@lists.rabbitmq.com, or directly at info@rabbitmq.com.
Yes, Ubuntu 9.04 Server Edition, aka "Jaunty Jackalope", now includes support for the emerging standard for messaging through RabbitMQ.
See Canonical's press release for more information on the release.
We look forward to hearing more from Ubuntu users and would welcome more feedback, bug requests and other contributions. Talk to us on irc.freenode.net #rabbitmq (see logs), or join our mailing list (or see archived messages).
The RabbitMQ team is pleased to announce the release of RabbitMQ 1.5.4.
This release has 'final' status and fixes a small number of bugs in the server, the startup and control scripts on Windows, and the Debian/RPM packaging. Also included are some minor enhancements to the way the server can be configured. The RabbitMQ clients have remained unchanged.
For details see the release notes.
Binary and source distributions of the new release can be found in the usual place
We recommend that all users of earlier versions of RabbitMQ upgrade to this latest release.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us via the RabbitMQ discussion list at rabbitmq-discuss@lists.rabbitmq.com, or directly at info@rabbitmq.com.
The RabbitMQ and AMQP team gave a presentation at QCon London last week. Slides presented are available here:
See also:
If you're looking for a place to start try here.
The LShift/RabbitMQ team is pleased to announce its second visit to Qcon London, please do come and say hello.
In honour of the event, and while we work on a new website, we produced this overview of how to use RabbitMQ.
The RabbitMQ team is pleased to announce the release of RabbitMQ 1.5.3.
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.
For details see the release notes.
Binary and source distributions of the new release can be found in the usual place, at http://www.rabbitmq.com/download.html.
We recommend that all users of earlier versions of RabbitMQ upgrade to this latest release.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us via the RabbitMQ discussion list at rabbitmq-discuss@lists.rabbitmq.com, or directly at info@rabbitmq.com.
The RabbitMQ team is pleased to announce the release of RabbitMQ 1.5.1.
This release has 'final' status and fixes a number of bugs in the server, the .net client, and the Debian/RPM packaging.
For details see the release notes.
Binary and source distributions of the new release can be found in the usual place, at http://www.rabbitmq.com/download.html.
We recommend that all users of earlier versions of RabbitMQ upgrade to this latest release.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us via the RabbitMQ discussion list at rabbitmq-discuss@lists.rabbitmq.com, or directly at info@rabbitmq.com.
The RabbitMQ team is pleased to announce the release of RabbitMQ 1.5.0.
This release has beta status and focuses on the following areas:
For details see the release notes.
Binary and source distributions of the new release can be found in the usual place, at http://www.rabbitmq.com/download.html.
We recommend that all users of earlier versions of RabbitMQ upgrade to this latest release.
As always, we welcome any questions, bug reports, and other feedback on this release, as well as general suggestions for features and enhancements in future releases. Mail us via the RabbitMQ discussion list at rabbitmq-discuss@lists.rabbitmq.com, or directly at info@rabbitmq.com.
It will start at 6:30pm and be at the LShift offices in London. A few beers may be provided and some RabbitMQ t-shirts are available for people who don't have one. Please let us know if you're coming.
Matthias Radestock (LShift TD), Tony Garnock-Jones (LShift Senior Developer) and Alexis Richardson (CohesiveFT CEO) spoke at the Google London meeting.
The presentation dealt with the AMQP protocol, how we built our Erlang implementation of it (RabbitMQ), and how it might address, eg., Twitter's scaling problems.
Further details are available at Google's developer blog..
The RabbitMQ team is pleased to announce the release of RabbitMQ 1.4.0.
This release has beta status, and switches to the use of a DFSG-free JSON-formatted specification document, includes bug fixes for a number of race conditions and non-compliances with the protocol specification, includes several performance improvements for large numbers of queues, fixes aspects of the Debian and RPM packaging, and improves upon the error reporting and general performance of the server.
Further details are available here.
You can also join our mailing list to keep up-to-date with the latest developments and discussion.