<div dir="ltr">Congrads on getting a new release out! :-)<br>Now the only thing missing for me is the flow-to-disk scenario and I'm all good :-D<br><br>I have 2 questions:<br>1) Have you managed to test the memory based flow control feature on Windows prior to the release? (it wasn't mention in the documentation like the MacOSX issue)<br>
<br>2) What would be the right way of upgrading rabbitmq on a running server without shutting it down? (I know erlang supports this feature but I failed to find something about it in the documentation). <br><br>3) Can you elaborate more on the memory based flow throttling and what is the behavior of clients when they get the channel.flow command? <br>
<br>Thanks,<br>Eran<br><br><br><div class="gmail_quote">On Thu, Dec 18, 2008 at 1:44 PM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@lshift.net">matthias@lshift.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
The RabbitMQ team is pleased to announce the release of RabbitMQ 1.5.0.<br>
<br>
This release has beta status and focuses on the following areas:<br>
<br>
- removal of tickets and realms<br>
- implementation of 'queue.unbind'<br>
- producer throttling when running low on memory<br>
- improved scalability of queue and binding creation and deletion<br>
- disabled Nagle for more consistent latency<br>
- added several management/info commands to rabbitmqctl<br>
- bug fixes in the area of connection and channel closure<br>
- support the latest Erlang/OTP release (R12B-5)<br>
- improved configurability via environment variables<br>
<br>
For details see the attached release notes.<br>
<br>
Binary and source distributions of the new release can be found in the usual place, at <a href="http://www.rabbitmq.com/download.html" target="_blank">http://www.rabbitmq.com/download.html</a><br>
<br>
We recommend that all users of earlier versions of RabbitMQ upgrade to this latest release.<br>
<br>
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 <a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.rabbitmq.com</a>, or directly at <a href="mailto:info@rabbitmq.com" target="_blank">info@rabbitmq.com</a>.<br>
<br>
<br>
Regards,<br>
<br>
The RabbitMQ Team<br>
<br>
<br>Release: RabbitMQ 1.5.0<br>
Status : beta<br>
<br>
Release Highlights<br>
==================<br>
<br>
server<br>
------<br>
bug fixes<br>
- support running on top of the latest Erlang/OTP release (R12B-5)<br>
- maintain effect visibility guarantees in cross-node routing<br>
- reduce likelihood of timeouts when channels interact with a large<br>
number of queues<br>
- graceful handling of some corner cases in abrupt client disconnect<br>
<br>
enhancements<br>
- remove tickets and realms<br>
- improve scalability of queue and binding creation and deletion<br>
- add 'queue.unbind' command to protocol<br>
- disable Nagle for more consistent latency<br>
- throttle producers with 'channel.flow' when running low on memory<br>
Note that this feature is disabled by default; please see<br>
<a href="http://www.rabbitmq.com/admin-guide.html#memsup" target="_blank">http://www.rabbitmq.com/admin-guide.html#memsup</a> for details.<br>
- remove a few spurious errors in the logs<br>
- show the actual listening IP & port in logs<br>
- improve rabbitmqctl:<br>
- add a few useful info commands<br>
- add a 'reopen_logs' command to assist in log management<br>
- add a '-q' flag to suppress informational messages and thus<br>
facilitate post-processing of the output<br>
- write errors to stderr instead of stdout<br>
<br>
Java client<br>
-----------<br>
bug fixes<br>
- eliminate several race condition in connection and channel closure<br>
that could result in deadlock<br>
- always respond to a server's 'connection.close' and 'channel.close'<br>
- prevent interference between interal locking on channels and<br>
application-level locking<br>
<br>
enhancements<br>
- remove tickets and realms<br>
- support 'queue.unbind'<br>
- disable Nagle for more consistent latency<br>
- react to server-issued 'channel.flow' by (un)blocking producers<br>
- add channel.abort method to unconditionally and idempotently close a<br>
channel<br>
- complete the set of channel and connection close and abort methods<br>
<br>
.net client<br>
-----------<br>
bug fixes<br>
- eliminate "Cannot access a disposed object" exception in connection<br>
closure and disposal<br>
- correct heartbeat logic to prevent spurious timeouts when not idling<br>
<br>
enhancements<br>
- remove tickets and realms<br>
- support 'queue.unbind'<br>
- disable Nagle for more consistent latency<br>
- react to server-issued 'channel.flow' by (un)blocking producers<br>
- add IModel.abort method to unconditionally and idempotently close a<br>
channel<br>
- complete the set of channel and connection close and abort methods<br>
<br>
building & packaging<br>
--------------------<br>
bug fixes<br>
- correct locations of libraries et al on 64bit rpm systems<br>
<br>
enhancements<br>
- detect upgrade from pre-1.5.0 and warn/ask user (under debian & rpm)<br>
- comply with debian and rpm packaging policies and guidelines<br>
- prevent accidental executing of scripts as non-root user under<br>
debian & rpm<br>
- read /etc/default/rabbitmq in scripts on Unix-y systems, with env<br>
vars taking precedence over vars set in that file and the defaults<br>
used by the scripts<br>
- prefix env vars with 'RABBITMQ_'<br>
- allow script execution from anywhere (not just the scripts' dir)<br>
- add script & instructions to start RabbitMQ as a Windows service<br>
- add 'status' command to init.d script under debian & rpm<br>
- automatic log rotation under debian & rpm<br>
- use simplejson.py instead of json.py in code generation, thus<br>
allowing use of Python 2.6<br>
<br>
<br>
Upgrading<br>
=========<br>
<br>
The database schema has changed between RabbitMQ-1.4.0 and this<br>
release. When the RabbitMQ server detects the presence of an old<br>
database, it moves it to a backup location, creates a fresh, empty<br>
database, and logs a warning.<br>
<br>
If your RabbitMQ installation contains important data, such as user<br>
accounts, durable exchanges and queues, or persistent messages, then<br>
we recommend you contact <a href="mailto:support@rabbitmq.com">support@rabbitmq.com</a> for assistance with the<br>
upgrade.<br>
<br>
<br>
Credits<br>
=======<br>
<br>
We would like to thank the following individuals for submitting bug<br>
reports and feedback that we incorporated into this release:<br>
<br>
Alister Morton<br>
Aman Gupta<br>
Andrius Norkaitis<br>
Barry Pedersen<br>
Benjamin Black<br>
Benjamin Polidore<br>
Brian Sullivan<br>
David Corcoran<br>
Dmitriy Samovskiy<br>
Edwin Fine<br>
Eran Sandler<br>
Esteve Fernandez<br>
Ezra Zygmuntowicz<br>
Ferret<br>
Gavin Bong<br>
Geoffrey Anderson<br>
Holger Hoffstätte<br>
Jacek Korycki<br>
John Leuner<br>
Jonatan Kallus<br>
Jonathan McGee<br>
Kyle Sampson<br>
Leo Martins<br>
Maarten Engelen<br>
Nathan Woodhull<br>
Nigel Verdon<br>
Paul Jones<br>
Pete Kay<br>
Peter Kieltyka<br>
Sarah Jelinek<br>
Sean Treadway<br>
Steve Jenson<br>
Terry Jones<br>
Vadim Zaliva<br>
Valentino Volonghi<br>
<br>_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
<br></blockquote></div><br></div>