转载

RabbitMQ v3.6.10 Milestone 2 发布，AMQP消息服务器

RabbitMQ是实现AMQP（高级消息队列协议）的消息中间件的一种，最初起源于金融系统，用于在分布式系统中存储转发消息，在易用性、扩展性、高可用性等方面表现不俗。消息中间件主要用于组件之间的解耦，消息的发送者无需知道消息使用者的存在，反之亦然。

AMQP 里主要要说两个组件：Exchange 和 Queue （在 AMQP 1.0 里还会有变动），如下图所示，绿色的 X 就是 Exchange ，红色的是 Queue ，这两者都在 Server 端，又称作 Broker ，这部分是 RabbitMQ 实现的，而蓝色的则是客户端，通常有 Producer 和 Consumer 两种类型。

更新日志

Bug 修复

Non-numerical values for numerical stats are now handled safety by stats aggregation. For example, if free disk space monitor had to stop reporting data because it could not parse external tool output that would break HTTP API GET /api/overview responses.

GitHub issue: rabbitmq-management#375.

Stats are no longer emitted for connections that are not considered to be in the fully initialised state.

GitHub issue: rabbitmq-management-agent#42
POST requests now instruct clients to close TCP connections.

In some popular browsers (Chrome, Internet Explorer) a POST request followed by an immediate GETrequest
would result in a 400 response. Other browsers do no exhibit this behaviour. Since HTTP API is not meant to be
on the hot code path and most requests are GET ones, disabling persistent HTTP connections
for POST requests is a reasonable trade-off.

GitHub issue: rabbitmq-management#377
Sample retention policies are now validated more strictly to avoid configurations that
are not supported and will lead to exceptions.

GitHub issue: rabbitmq-management-agent#41
UI operation for binding deletion did not respect optional (extra) binding arguments.

GitHub issue: rabbitmq-management#243