@@ -47,6 +47,67 @@ Release notes can be found on GitHub at [rabbitmq-server/release-notes](https://
47
47
48
48
GitHub issue: [ #9222 ] ( https://github.com/rabbitmq/rabbitmq-server/pull/9222 )
49
49
50
+ * Avoids a potential exception in the credit flow subsystem.
51
+
52
+ Contributed by @Ayanda-D .
53
+
54
+ GitHub issue: [ #9433 ] ( https://github.com/rabbitmq/rabbitmq-server/pull/9433 )
55
+
56
+ * Classic queues v2 (CQv2) that had priorities enabled were reporting their storage version
57
+ incorrectly.
58
+
59
+ Contributed by @gomoripeti (CloudAMQP).
60
+
61
+ GitHub issue: [ #9370 ] ( https://github.com/rabbitmq/rabbitmq-server/issues/9370 )
62
+
63
+ #### Enhancements
64
+
65
+ * Channels that had many thousands of consumers (usually due to a consumer leak in the application)
66
+ now consume a lot less CPU resources when the channel is closed.
67
+
68
+ As part of this optimization, individual ` consumer.deleted ` internal events are no
69
+ longer emitted when a channel is closed, only a ` channel.closed ` event is. This also
70
+ help reduce audit event log size, since those ` consumer.deleted ` events provided
71
+ no useful information in this context.
72
+
73
+ Contributed by @SimonUnge (AWS).
74
+
75
+ GitHub issue: [ #9356 ] ( https://github.com/rabbitmq/rabbitmq-server/pull/9356 )
76
+
77
+ * Initial forward compatibility with later Erlang 26.x and 27.0 releases.
78
+
79
+ GitHub issue: [ #9485 ] ( https://github.com/rabbitmq/rabbitmq-server/pull/9485 )
80
+
81
+ * Nodes now log boot time at info level instead of debug. This piece of information
82
+ can be useful during root cause analysis.
83
+
84
+ Contributed by @johanrhodin (CloudAMQP).
85
+
86
+ GitHub issue: [ #9466 ] ( https://github.com/rabbitmq/rabbitmq-server/pull/9466 )
87
+
88
+ * Channel interceptors (defined by plugins) now can return one more type of errors.
89
+
90
+ Contributed by @Ayanda-D .
91
+
92
+ GitHub issue: [ #9459 ] ( https://github.com/rabbitmq/rabbitmq-server/pull/9459 )
93
+
94
+
95
+ ### CLI Tools
96
+
97
+ #### Bug Fixes
98
+
99
+ * ` rabbitmqctl delete_queue ` now handles more queue replica failure scenarios
100
+ (that were previously handled by client operations and the HTTP API but not CLI tools).
101
+
102
+ Contributed by @Ayanda-D .
103
+
104
+ GitHub issue: [ #9324 ] ( https://github.com/rabbitmq/rabbitmq-server/pull/9324 )
105
+
106
+ * ` rabbitmq-streams delete_replica ` now handles scenarios where the replica is hosted
107
+ on a node that is not accessiable (reachable).
108
+
109
+ GitHub issue: [ #9282 ] ( https://github.com/rabbitmq/rabbitmq-server/issues/9282 )
110
+
50
111
51
112
### MQTT Plugin
52
113
@@ -58,9 +119,31 @@ Release notes can be found on GitHub at [rabbitmq-server/release-notes](https://
58
119
GitHub issue: [ #9281 ] ( https://github.com/rabbitmq/rabbitmq-server/pull/9281 )
59
120
60
121
122
+ ### AMQP 1.0 Plugin
123
+
124
+ #### Bug Fixes
125
+
126
+ * Listing AMQP 1.0 connections in a system that had both AMQP 1.0 and AMQP 0-9-1 clients connected
127
+ resulted in exceptions logged and partial results returned to CLI tools.
128
+
129
+ GitHub issue: [ #9371 ] ( https://github.com/rabbitmq/rabbitmq-server/issues/9371 )
130
+
131
+
132
+ ### Prometheus Plugin
133
+
134
+ #### Enhancements
135
+
136
+ * The plugin now exposes a new gauge, ` rabbitmq_unreachable_cluster_peers_count ` , that indicates how many cluster
137
+ peers ** cannot** be reached by this node.
138
+
139
+ Contributed by @gomoripeti (CloudAMQP).
140
+
141
+ GitHub issues: [ #2508 ] ( https://github.com/rabbitmq/rabbitmq-server/issues/2508 ) , [ #9465 ] ( https://github.com/rabbitmq/rabbitmq-server/pull/9465 )
142
+
143
+
61
144
## Dependency Upgrades
62
145
63
- * ` osiris ` was upgraded to [ ` 1.6.4 ` ] ( https://github.com/rabbitmq/osiris/tags )
146
+ * ` osiris ` was upgraded to [ ` 1.6.7 ` ] ( https://github.com/rabbitmq/osiris/tags )
64
147
65
148
66
149
## Dependency Upgrades
0 commit comments