- 4.01 MB rabbitmq-server-3.5.1-1.noarch.rpm
- 4.01 MB rabbitmq-server-3.5.1-1.suse.noarch.rpm
- 3.89 MB rabbitmq-server-3.5.1.exe
- 3.98 MB rabbitmq-server-generic-unix-3.5.1.tar.gz
- 16.7 MB rabbitmq-server-mac-standalone-3.5.1.tar.gz
- 4.07 MB rabbitmq-server-windows-3.5.1.zip
- 3.97 MB rabbitmq-server_3.5.1-1_all.deb
- Source code (zip)
- Source code (tar.gz)
- Introduce a new
channellog category for channel log messages (rabbitmq/rabbitmq-server#74).
consumer_closedevents are emitted for the actually closed channels only, not all of them (since 3.3.0, rabbitmq/rabbitmq-server#86). The events were filtered later in the management plugin so the behaviour was correct. However, the broker did way too much work.
- Ensure the number of
x-deathmessage headers doesn't grow indefinitely (rabbitmq/rabbitmq-server#78). Now, there is a single entry for each
- Adjust the file read buffer cache size to avoid useless reads (since 3.5.0, rabbitmq/rabbitmq-server#69). Before this fix, reading a file backward would cause the buffer to be filled and thrown away quickly, leading to a large I/O bandwidth consumption.
- Ensure the priority queue plugin reports its memory consumption properly (since 3.5.0, rabbitmq/rabbitmq-server#67). Before this fix, the queue might not be paged out under memory pressure.
- Prevent a crash while synchronising paged out priority queues (since 3.5.0, rabbitmq/rabbitmq-server#65). This was caused by priority queues accessing message properties without checking their existence.
- Pass the PID file to
rabbitmq-server.ocf, exactly like Debian- and Red Hat-flavour init scripts (since 2.6.0, rabbitmq/rabbitmq-server#72).
Plugin: AMQP 1.0
- Fix heartbeats (rabbitmq/rabbitmq-amqp1.0#6).
- Respond with a protocol error if a disposition frame is incorrect (rabbitmq/rabbitmq-amqp1.0#8).
- Fix a crash if the
initial-delivery-countis not 0 (rabbitmq/rabbitmq-amqp1.0#9).
Client library: Java
ConnectionFactory's custom threadFactory (rabbitmq/rabbitmq-java-client#33).
Client library: .NET
- Add a test case to ensure consumers are properly resumed after automatic recovery (rabbitmq/rabbitmq-dotnet-client#50).
- Ensure no bindings are lost during automatic recovery (since 3.4.0, rabbitmq/rabbitmq-dotnet-client#43).
- Ensure client certificates are not mandatory with SSL connections (rabbitmq/rabbitmq-dotnet-client#46). There was a previous attempt in fixing this but it broke the ability to require specific SSL versions (since 3.5.0, rabbitmq/rabbitmq-dotnet-client#44).
ConsumerWorkServiceuses the scheduler it is constructed with (since 3.5.0, rabbitmq/rabbitmq-dotnet-client#40).
Building and packaging
make checkoutto retry if GitHub closes the connection (rabbitmq/rabbitmq-public-umbrella#17).
make sync_gitusertargets to synchronize Git remote and user/email accross the umbrella and all its subrepositories (rabbitmq/rabbitmq-public-umbrella#5).
- Make internal database files private to the group (eg.
make up_cto work with detached HEAD. This allows to checkout a tag again (since 3.5.0, rabbitmq/rabbitmq-public-umbrella#6).
make statusso it walks through directories correctly (rabbitmq/rabbitmq-public-umbrella#13).
$(MAKE)instead of a hard-coded
To upgrade a non-clustered RabbitMQ simply install the new version. All configuration and persistent message data are retained.
To upgrade a RabbitMQ cluster, follow the instructions at:
Source code archives
Warning: The source code archives provided by GitHub only contain the source of the broker, not the plugins or the client libraries. Please download the archives available from the official download page: