1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
|
Release: RabbitMQ 2.4.0
Release Highlights
==================
server
------
bug fixes
- in a cluster, don't fail with an internal-error when re-declaring a
queue on a connection to a node other than the queue's "home" node
- in a cluster, report a not-found error instead of internal-error
when attempting to re-declare a durable queue whose node is
unavailable
- do not ignore the RABBITMQ_LOG_BASE variable on Windows
- fix a bug causing SSL connections to die on Erlang prior to R14
when using "rabbitmqctl list_connections" with the SSL options
- various minor fixes
enhancements
- greatly speed up routing for topic exchanges with many bindings
- propagate memory alarms across cluster, thus reacting better to
memory pressure on individual nodes.
- sender-selected distribution (i.e. add support for the CC and BCC
headers). See
https://www.rabbitmq.com/extensions.html#sender-selected-distribution
for more information.
- server-side consumer cancellation notifications. See
https://www.rabbitmq.com/extensions.html#consumer-cancel-notify
for more information.
- have the server present its AMQP extensions in a "capabilities"
field in server-properties. See
https://www.rabbitmq.com/extensions.html#capabilities
for more information.
- determine file descriptor limits accurately on Windows, usually
resulting in much higher limits than previously, which allows more
connections and improves performance
- indicate in the logs when the file descriptor limit has been reached
(causing the server to not accept any further connections)
- allow SASL mechanisms to veto themselves based on socket type
- rename rabbitmq.conf to rabbitmq-env.conf, to avoid confusion with
rabbitmq.config
- improve performance of publisher confirms
- various other minor enhancements and performance improvements
java client
-----------
bug fixes
- prevent stack overflow when connections have large numbers channels
- do not require a working reverse DNS when establishing connections
enhancements
- ConnectionFactory accepts a connection timeout parameter
- allow prioritisation of SASL mechanisms
- support for server-side consumer cancellation notifications
- have the client present its AMQP extensions in a "capabilities"
field in client-properties
- rename ReturnListener.handleBasicReturn to handleReturn
.net client
-----------
bug fixes
- WCF bindings specified in configuration files are no longer ignored
enhancements
- support for server-side consumer cancellation notifications
- have the client present its AMQP extensions in a "capabilities"
field in client-properties
- support IPv6
management plugin
-----------------
bug fixes
- hide passwords in the web UI
- fix rabbitmqadmin's handling of Unicode strings
enhancements
- present the managed socket and open file counts and respective limits
- better memory usage reporting for hibernating queues
- better support for serving the web interface through a proxy
- allow users to choose which node a queue is declared on
- show memory alarm states for nodes
- show statistics for basic.returns
- publish/receive messages via HTTP; this is intended for testing /
learning / debugging, not as a general solution for HTTP messaging
STOMP plugin
------------
bug fixes
- prevent crash when publishing from STOMP, but subscribing from
non-STOMP
- correctly process publishes spanning multiple network packets
- do not crash when publishing with undefined headers
- receipts for SEND frames wait on confirms
- do not issue a DISCONNECT with receipt when a clean shutdown has
*not* occurred
enhancements
- add documentation. See https://www.rabbitmq.com/stomp.html
- significant performance improvements
- extend flow-control on back pressure through the STOMP gateway
preventing the STOMP from overloading the server
- support for the "persistent" header
- support for multiple NACK
SSL authentication mechanism plugin
-----------------------------------
enhancements
- only offer this mechanism on SSL connections
build and packaging
-------------------
enhancements
- Windows installer for the broker
- remove the rabbitmq-multi script in order to simplify startup and
improve error reporting
- add the "cond-restart" and "try-restart" options to the init script
- specify runlevels in the rabbitmq-server.init script
- make the java client jar an OSGi bundle
- Debian package only depends on erlang-nox
Upgrading
=========
To upgrade a non-clustered RabbitMQ from release 2.1.1 or later, simply
install the new version. All configuration and persistent message data
is retained.
To upgrade a non-clustered RabbitMQ from release 2.1.0, first upgrade
to 2.1.1 (which retains all data), and then to the current version as
described above.
To upgrade a clustered RabbitMQ or from releases prior to 2.1.0, if
the RabbitMQ installation does not contain any important data then
simply install the new version. RabbitMQ will move the existing data
to a backup location before creating a fresh, empty database. A
warning is recorded in the logs. If your RabbitMQ installation
contains important data then we recommend you contact
rabbitmq-sales@pivotal.io for assistance with the upgrade.
|
