blob: f2b3c86f78bd257ce00d48991f463e99a273e035 (
plain)
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
|
## RabbitMQ 3.6.4
`3.6.4` is a maintanence release.
### Server
#### Bug Fixes
* Nodes on Windows will successfully start if Erlang is installed in a directory with spaces
in the path.
GitHub issue: [rabbitmq-server#859](https://github.com/rabbitmq/rabbitmq-server/issues/859)
* Node health check is now node-local, as it was meant to be.
GitHub issue: [rabbitmq-server#818](https://github.com/rabbitmq/rabbitmq-server/issues/818)
* Queue deletion and termination will no longer leave "tomb stone" messages in message store
files. This eliminates the confusing behavior when a node or cluster having no messages
enqueued could have many thousands of such "marker" messages in the message store.
GitHub issue: [rabbitmq-server#839](https://github.com/rabbitmq/rabbitmq-server/issues/839)
* `rabbitmqctl cluster_status` will now output an accurate error message
if invoked shortly after a node was removed from the cluster and the node cannot be
contacted.
GitHub issue: [rabbitmq-server#894](https://github.com/rabbitmq/rabbitmq-server/pull/894)
Contributed by Peter Lemenkov (Red Hat)
#### Enhancements
* Erlang VM scheduler binding type default has changed to `db`. This means fewer
CPU context switches for some workloads.
GitHub issue: [rabbitmq-server#612](https://github.com/rabbitmq/rabbitmq-server/issues/612)
### Management Plugin
#### Bug Fixes
* HTTP API is now compatible with Erlang 19.0.
GitHub issue: [rabbitmq-management#244](https://github.com/rabbitmq/rabbitmq-management/issues/244)
* Temporary tables are no longer named using atoms, preventing a potential
exhaustion of the runtime atom table.
GitHub issue: [rabbitmq-management#245](https://github.com/rabbitmq/rabbitmq-management/issues/245)
* Cluster links and traffic charts are correctly displayed again
GitHub issue: [rabbitmq-management#250](https://github.com/rabbitmq/rabbitmq-management/issues/250)
* Runtime metric charts now have a description pop-up associated with them.
GitHub issue: [rabbitmq-management#247](https://github.com/rabbitmq/rabbitmq-management/issues/247)
### AMQP 1.0 plugin
#### Bug fixes
* When an AMQP 1.0 specified its own list of source outcomes in a link
attachment, it caused a crash of its session on the server. Now a
protocol error is raised if the list contains invalid outcomes.
GitHub issue: [rabbitmq-amqp1.0#31](https://github.com/rabbitmq/rabbitmq-amqp1.0/issues/31)
### Java Client
#### Enhancements
* The client will now try to use TLS v1.2 and v1.1 before falling back to v1.0 by default.
GitHub issue: [rabbitmq-java-client#155](https://github.com/rabbitmq/rabbitmq-java-client/issues/155)
|
