<div class="gmail_quote"><br>Great work guys! I'll look forward to trying out the latest version :)<div><br></div><div>Cal<br><br><div class="gmail_quote"><div><div></div><div class="h5">On Wed, Aug 25, 2010 at 11:01 AM, Michael Bridgen <span dir="ltr"><<a href="mailto:mikeb@rabbitmq.com" target="_blank">mikeb@rabbitmq.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div></div><div class="h5">We the RabbitMQ team are delighted to announce the release of RabbitMQ<br>
2.0.0.<br>
<br>
This release includes a rewritten message store that pages messages to<br>
disk to relieve memory pressure, and support for AMQP 0-9-1. �There are<br>
many other more modest additions, such as an implementation of<br>
basic.reject, and queue leases. �For details see the attached release notes.<br>
<br>
Binary and source distributions of the new release can be found in the<br>
usual place at <a href="http://www.rabbitmq.com/download.html" target="_blank">http://www.rabbitmq.com/download.html</a><br>
<br>
This now includes binary packages of plugins, at<br>
<a href="http://www.rabbitmq.com/plugins.html" target="_blank">http://www.rabbitmq.com/plugins.html</a>. �Please note the caveats there.<br>
<br>
Due to an issue we're currently seeing with the nexus/sonatype<br>
maven repository, the 2.0.0 release is not yet available in maven. We<br>
will rectify this as soon as we can.<br>
<br>
We recommend that all users of earlier versions of RabbitMQ upgrade to<br>
this latest release.<br>
<br>
As always, we welcome any questions, bug reports, and other feedback on<br>
this release, as well as general suggestions for features and<br>
enhancements in future releases. Mail us via the RabbitMQ discussion<br>
list at <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.rabbitmq.com</a>, or directly at<br>
<a href="mailto:info@rabbitmq.com" target="_blank">info@rabbitmq.com</a>.<br>
<br>
<br>
Regards,<br>
<br>
The RabbitMQ Team<br>
<br>
<br>
<br></div></div><div><div></div><div class="h5">Release: RabbitMQ 2.0.0<br>
<br>
Release Highlights<br>
==================<br>
<br>
server<br>
------<br>
bug fixes<br>
- correct file descriptor limits on Windows, preventing crashes due to<br>
�exceeding the limit<br>
- fix bug that resulted in 'rabbitmqctl status' reporting disk nodes<br>
�as ram nodes<br>
- tx.commit no longer fails when participating queues are deleted<br>
�during the lifetime of the transaction<br>
- more robust logic to detect changes in the data layout between<br>
�rabbit versions and thus guard against upgrade failures<br>
<br>
enhancements<br>
- new persister<br>
�- the volume of messages rabbit can hold on to is bounded by disk<br>
� �space (in previous versions it was bounded by memory)<br>
�- rabbit optimises memory usage by paging messages out to / in from<br>
� �disk as needed<br>
�- consistently high performance regardless of retained message<br>
� �volume (previous versions would slow down considerably as the<br>
� �persisted message volume grew)<br>
�- consistently fast startup regardless of volume of persisted data<br>
� �(previous versions would require time proportional to the amount<br>
� �of data)<br>
�- better performance for concurrent transactions (in previous<br>
� �version the rate at which queues could handle transactions<br>
� �involving persistent messages was fixed)<br>
- implement AMQP 0-9-1, in addition to 0-8 - see<br>
�<a href="http://www.rabbitmq.com/specification.html" target="_blank">http://www.rabbitmq.com/specification.html</a><br>
- instrumentation for asynchronous statistics events, emitting more<br>
�stats than currently available and laying the foundation for<br>
�monitoring a busy broker without crippling performance -<br>
�see <a href="http://www.rabbitmq.com/blog/2010/08/06/management-monitoring-and-statistics/" target="_blank">http://www.rabbitmq.com/blog/2010/08/06/management-monitoring-and-statistics/</a><br>
- more effective flow control mechanism that does not require<br>
�cooperation from clients and reacts quickly to prevent the broker<br>
�from exhausing memory - see <a href="http://www.rabbitmq.com/extensions.html#memsup" target="_blank">http://www.rabbitmq.com/extensions.html#memsup</a><br>
- implement basic.reject - see<br>
<a href="http://www.rabbitmq.com/blog/2010/08/03/well-ill-let-you-go-basicreject-in-rabbitmq/" target="_blank">http://www.rabbitmq.com/blog/2010/08/03/well-ill-let-you-go-basicreject-in-rabbitmq/</a><br>
- simplify plugin activation by moving it into the server startup<br>
- permit upgrades of Erlang w/o breaking rabbit servers with activated<br>
�plugins<br>
- introduce support for queue leases - see <a href="http://www.rabbitmq.com/extensions.html#queue-leases" target="_blank">http://www.rabbitmq.com/extensions.html#queue-leases</a><br>
- improve the setting of permissions, making it easer to use and<br>
�introducing a way to grant no permissions at all - see <a href="http://www.rabbitmq.com/admin-guide.html#management" target="_blank">http://www.rabbitmq.com/admin-guide.html#management</a><br>
- delete exclusive queues synchronously on server-initiated connection<br>
�close (rather than just client-initiated)<br>
<br>
java client<br>
-----------<br>
bug fixes<br>
- prevent spurious timeout exceptions that theoretically could have<br>
�arisen due to spurios thread wake-ups<br>
<br>
enhancements<br>
- switch to AMQP 0-9-1 - see<br>
�<a href="http://www.rabbitmq.com/specification.html" target="_blank">http://www.rabbitmq.com/specification.html</a><br>
<br>
.net client<br>
-----------<br>
bug fixes<br>
- fix bug that caused incorrect responses to server-issued<br>
�channel.flow commands, which in turn resulted in connections getting<br>
�closed with an error.<br>
- make SSL connections work in Mono<br>
<br>
enhancements<br>
- implement AMQP 0-9-1, in addition to 0-8 and 0-9 - see<br>
�<a href="http://www.rabbitmq.com/specification.html" target="_blank">http://www.rabbitmq.com/specification.html</a><br>
- simplify the Subscription class and make it more versatile<br>
- improve documentation<br>
<br>
building & packaging<br>
--------------------<br>
bug fixes<br>
- correct location of rabbitmq.config file under macports - it now<br>
�lives in /opt/local/etc/rabbitmq/<br>
- "make docs_all" now works on more platforms<br>
<br>
enhancements<br>
- portable, binary plugin releases to simplify plugin installation -<br>
�see <a href="http://www.rabbitmq.com/plugins.html" target="_blank">http://www.rabbitmq.com/plugins.html</a><br>
- automatically create plugin directory, to streamline plugin<br>
�installation<br>
<br>
Upgrading<br>
=========<br>
The database schema and the format in which persistent messages are<br>
stored have both changed since the last release (1.8.1). When<br>
starting, the RabbitMQ server will detect the existence of an old<br>
database and will move it to a backup location, before creating a<br>
fresh, empty database, and will log a warning. If your RabbitMQ<br>
installation contains important data then we recommend you contact<br>
<a href="mailto:support@rabbitmq.com" target="_blank">support@rabbitmq.com</a> for assistance with the upgrade.<br>
<br>
<br></div></div>_______________________________________________<br>
rabbitmq-discuss mailing list<div class="im"><br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.rabbitmq.com</a><br>
</div><div class="im"><a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
<br></div></blockquote></div><br><br clear="all"><br>-- <br><p style="color:rgb(0, 51, 102);font-weight:bold"><span style="border-collapse:separate;font-family:arial;line-height:normal;font-size:small">Cal Leeming</span></p>
<p style="color:rgb(0, 51, 102);font-weight:bold">
Operational Security & Support Team<br></p><p style="border-bottom-width:1px;border-bottom-style:solid;border-bottom-color:rgb(204, 204, 204);padding-bottom:25px"><b>Out of Hours:�</b>+44 (07534) 971120 |�<b>Support Tickets:�</b><a href="mailto:support@simplicitymedialtd.co.uk" style="color:rgb(49, 132, 173)" target="_blank">support@simplicitymedialtd.co.uk</a>�<br>
<b>Fax:�</b>+44 (02476) 578987�|�<b>Email:�</b><a href="mailto:cal.leeming@simplicitymedialtd.co.uk" style="color:rgb(49, 132, 173)" target="_blank">cal.leeming@simplicitymedialtd.co.uk</a>�</p><div><span style="line-height:13px;font-size:10px;color:rgb(185, 184, 184)">Simplicity Media Ltd. All rights reserved.<br>
</span></div><div><span style="line-height:13px;font-size:10px;color:rgb(185, 184, 184)">Registered company number�7143564<span></span><span></span></span></div><br>
</div>
</div><br><br clear="all"><br>-- <br><p style="color:rgb(0, 51, 102);font-weight:bold"><span style="border-collapse:separate;font-family:arial;line-height:normal;font-size:small">Cal Leeming</span></p><p style="color:rgb(0, 51, 102);font-weight:bold">
Operational Security & Support Team<br></p><p style="border-bottom-width:1px;border-bottom-style:solid;border-bottom-color:rgb(204, 204, 204);padding-bottom:25px"><b>Out of Hours:�</b>+44 (07534) 971120 |�<b>Support Tickets:�</b><a href="mailto:support@simplicitymedialtd.co.uk" style="color:rgb(49, 132, 173)" target="_blank">support@simplicitymedialtd.co.uk</a>�<br>
<b>Fax:�</b>+44 (02476) 578987�|�<b>Email:�</b><a href="mailto:cal.leeming@simplicitymedialtd.co.uk" style="color:rgb(49, 132, 173)" target="_blank">cal.leeming@simplicitymedialtd.co.uk</a>�</p><div><span style="line-height:13px;font-size:10px;color:rgb(185, 184, 184)">Simplicity Media Ltd. All rights reserved.<br>
</span></div><div><span style="line-height:13px;font-size:10px;color:rgb(185, 184, 184)">Registered company number�7143564<span></span><span></span></span></div><br>