[rabbitmq-discuss] RabbitMQ 1.6.0 release

[Darien Kindlund]

Hi Matthias,

Thanks for the update!  Couple of questions:
 - If we encounter any similar "persister timeout" errors logged via
STOMP adapter [that we saw in v1.5.x], should we post our findings to
the list?
 - If the persister bug has been fixed, does that mean the
prioritization feature may get added in v1.6.1? ;)
 - Does the STOMP adapter need to be updated/tested before using with
v1.6.0?  If the current version is fine, can Tony tag the latest
stable as rabbitmq_v1_6_0?
- Also, does rabbitmq-c work with v1.6.0?
- Assuming we don't find any bugs with v1.6.0, is the standard
procedure to just mark v1.6.0 status as "stable" (from "beta"), or
were you planning on bumping the version number (and updating the
packages) to reflect a "stable" status?

Regards,
-- Darien

On Wed, Jun 17, 2009 at 7:35 AM, Matthias Radestock<matthias at lshift.net> wrote:
> 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 attached 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 at lists.rabbitmq.com, or directly at
> info at rabbitmq.com.
>
>
> Regards,
>
> The RabbitMQ Team
>
>
> Release: RabbitMQ 1.6.0
> Status : final
>
> Release Highlights
> ==================
>
> server
> ------
> bug fixes
> - eliminate potential memory leak of transactionally published
>  messages in certain system errors
> - prevent possible starvation of some consumers on channels that get
>  temporarily blocked due to backlogs
> - do not send more messages to backlogged channels when accepting a
>  new consumer
> - prevent possible message reordering in the event of temporary node
>  failure in a clustered setup
> - return 'not_found' error in all cases of 'queue.unbind' attempting
>  to remove a non-existing binding
>
> enhancements
> - implement AMQP's basic.qos' channel prefetch count limiting
> - implement AMQP 0-9/0-9-1's headers exchange type
> - introduce a permissions system which allows fine-grained access
>  control on resources involved in AMQP operations. See
>  http://www.rabbitmq.com/admin-guide.html#access-control for details
> - introduce 'alternate exchanges' to handle messages which are
>  otherwise unroutable. See
>  http://www.rabbitmq.com/extensions.html#alternate-exchange for
>  details
> - improve performance and stability under high load
> - reduce memory consumption
> - prefix all mnesia tables with "rabbit_" in order to prevent name
>  clashes with other Erlang applications, in particular ejabberd
> - handle rabbitmqctl commands with higher priority, thus ensuring that
>  answers are returned promptly even under high load
> - reduce severity of "connection closed abruptly" log event from
>  'error' to 'warning'
>
> Java client
> -----------
> enhancements
> - support extended list of table field types
>
> .net client
> -----------
> bug fixes
> - make unit tests work under .NET 2.0
>
> enhancements
> - rename public fields to avoid name clashes with properties that trip
>  up tools like PowerShell
> - suppress inclusion of spec comments in generated code due to
>  licensing issues
> - generate strong named (i.e. signed) assemblies. See the bottom of
>  http://www.rabbitmq.com/dotnet.html for details
>
> building & packaging
> --------------------
> enhancements
> - introduce wrapper scripts in macports, as in the Debian and RPM
>  packaging, which ensure the real scripts are run as the right
>  ('rabbitmq') user
> - remove build-time dependency on mnesia
> - trim Debian Erlang package dependencies
> - auto-generate the module list in rabbit.app, thus ensuring it is
>  always up to date
>
> Upgrading
> =========
>
> When upgrading from releases earlier than 1.5.3, note that the place
> from which the server startup and control scripts source configuration
> information on Unix systems has changed from /etc/default/rabbitmq to
> /etc/rabbitmq/rabbitmq.conf. If you have been using the former, just
> move the file to the latter location.  The /etc/default/rabbitmq file
> (/etc/sysconfig/rabbitmq on RPM-based systems) is still being sourced
> by the init.d script, but it should only contain settings directly
> affecting the behaviour of the init.d script, such as NODE_COUNT.
>
> The database schema has changed. When the RabbitMQ server detects the
> presence of an old database, it moves it to a backup location, creates
> a fresh, empty database, and logs a warning. If your RabbitMQ
> installation contains important data, such as user accounts, durable
> exchanges and queues, or persistent messages, then we recommend you
> contact support at rabbitmq.com for assistance with the upgrade.
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>