Project: RabbitMQ (App Definition and Development / Streaming & Messaging)
File: 3.6.1.md

RabbitMQ `3.6.1` is a maintenance release that includes a fix for CVE-2015-8786, a vulnerability in RabbitMQ management plugin. Purging a lazy queue could result in an exception GitHub issue: Ensure `epmd` is running before starting RabbitMQ node on Windows GitHub issue: Channel error could make broker unreachable Those errors were misleadingly logged as `channelterminationtimeout`, which the issue really was with unhandled messages from concurrently closed TCP socket process. GitHub issue: (Automatic) deletion of an auto-delete queue could lead to blocked channels GitHub issue: During (from scratch) queue sync, queue leader node didn't respect mirror alarm state. With large data sets this could drive mirror node out of memory. GitHub issue: Changing password for users with non-standard (think broker configuration) password hashing function, for example, those migrated from `3.5.x` releases, didn't update effective hashing function. GitHub issue: Heavy and/or prolonged `rabbitmqctl` use could exhaust Erlang VM atom table GitHub issue: "Min masters" queue leader location strategy could result in an error. GitHub issue: Fixed a race condition in `pause_minority` handling mode. GitHub issue: Significantly reduce possibility of a race condition when an exchange is deleted and immediately re-declared, e.g. by a federation link. This could result in a link operation being blocked, preventing nodes from stopping. GitHub issue: `amq.rabbitmq.log` messages now have information about originating node in message headers GitHub issue: `scripts/rabbitmq-env` now works with GNU sed 4.2.2 GitHub issue: Exceptions in VM memory use calculator no longer affect broker startup GitHub issue: capability is now advertised to clients GitHub issue: Paths with non-ASCII characters on Windows are now handled RabbitMQ now can be installed into a location with non-ASCII characters, e.g. when username contains them. GitHub issues: Configurable number of TCP connection acceptors Plus a x10 increase of the default. This helps with workloads where connection churn is very high (e.g. all clients are PHP Web apps that cannot maintain long-lived

GitHub issues: `rabbitmqctl cluster_status` now includes cluster-wide resource alarm status GitHub issue: Windows installer no longer jumps over installation log GitHub issue: Improved `rabbitmqctl reset` error messages GitHub issue: More unsigned field data types are supported. GitHub issue: Endpoints (hostnames) are now also accepted as a `java.util.List` GitHub issue: Autorecovering connections now shuffle hosts in a more reliable way GitHub issue: Binding recovery could fail GitHub issue: `Channel.queueDelete` could throw a `NullPointerException` GitHub issue: Autorecovering connections now use full list of provided hostnames during recovery GitHub issues: Significantly reduce possibility of a race condition when an exchange is deleted and immediately re-declared, e.g. by a federation link This rendered federation links dysfunctional. GitHub issue: CVE-2015-8786: user-provided query parameters `lengthsage` and `lengthsincr` had no validation and could be used to exhaust server resources. The attacker needs to have access to HTTP API (authenticate successfully and have sufficient tags to pass authorisation) in order to carry out the attack. There is no workaround for earlier releases. Kudos to Vladimir Ivanov (Positive Technologies) for the responsible disclosure. GitHub issue: Password hashing function is now included in exported definitions Those upgrading from versions earlier than `3.6.0` via definitions export won't have to temporarily set hashing function to MD5 to ensure export succeeds. GitHub issue: Internet Explorer (9+) compatibility restored GitHub issue: Internet Explorer 11 compatibility fixes GitHub issues: , When policy fails to be created with invalid paramaters a sensible error message will be displayed. GitHub issue: Federation link form now includes more settings (that are exchange- and queue-federation specific) GitHub issue: `password` and `depth` query parameters are now propagated to TLS options GitHub issue: `durable` and `persistent` headers weren't always used interchangeably, leading to non-durable subscriptions GitHub issue: Client heartbeat timeouts resulted in confusing error messages in broker log. GitHub issues: Cowboy options are now supported for TLS listeners. GitHub issue: Multi-byte UTF-8 characters are now handled by the bundled version of stomp.js. GitHub issue: Event timestamps are now in seconds, not milliseconds Per AMQP 0-9-1 spec. This is not a particularly great choice for events, so we will add an optional header with millisecond precision in a future release. GitHub issue: Note: this plugin is deprecated and its use is highly discouraged. RabbitmQ `3.6.x` support. GitHub issue: