You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 17, 2020. It is now read-only.
Restarting the node hosting the statistics database or just restarting the statistics database as described here drops information about channels.
The connections themselves are still working like nothing happened. I'd therefore conclude that the AMQP channels also still have to exist.
The call to the Management Website "/#/channels" lists no channels:
Although for the connections is listed that there is a channel associated with:
The call to the HTTP API "/api/channels" only lists an empty array as well:
[]
RabbitMQ Version 3.6.5 with Erlang Version 19.1
As the channel hold the information about what consumer is running on what connection that information would be quite useful to always have available without forcing clients to reconnect.
The text was updated successfully, but these errors were encountered:
Restarting the node hosting the statistics database or just restarting the statistics database as described here drops information about channels.
The connections themselves are still working like nothing happened. I'd therefore conclude that the AMQP channels also still have to exist.
![nochannels](https://cloud.githubusercontent.com/assets/19569510/20833926/6e5b65a2-b892-11e6-8ab2-4cabdd583af9.PNG)
![connections](https://cloud.githubusercontent.com/assets/19569510/20833898/52f888d0-b892-11e6-95ec-2791cad1bf45.PNG)
The call to the Management Website "/#/channels" lists no channels:
Although for the connections is listed that there is a channel associated with:
The call to the HTTP API "/api/channels" only lists an empty array as well:
RabbitMQ Version 3.6.5 with Erlang Version 19.1
As the channel hold the information about what consumer is running on what connection that information would be quite useful to always have available without forcing clients to reconnect.
The text was updated successfully, but these errors were encountered: