Skip to content
This repository has been archived by the owner on Nov 16, 2020. It is now read-only.

External port crash in rabbit_mgmt_external_stats:init/1 can affect other processes #12

Closed
michaelklishin opened this issue Feb 2, 2016 · 3 comments
Assignees

Comments

@michaelklishin
Copy link
Member

See this report. This is the same issue as in rabbitmq/rabbitmq-server#91, except in a different module.

The process should not stop in init/1, in fact, it should not attempt to retrieve the stats there, waiting for a moment is perfectly fine.

@michaelklishin
Copy link
Member Author

Re-assigning to @hairyhum per discussion with him. Thank you for taking over.

@hairyhum
Copy link
Contributor

hairyhum commented Feb 2, 2016

rabbit_mgmt_external_stats is not emiting any stats in init/1, it sends itself message to emit later. So it's not the same issue. Needs more investigation on impact.

@michaelklishin michaelklishin modified the milestones: 3.6.x, 3.6.1 Feb 25, 2016
@michaelklishin michaelklishin removed this from the 3.6.x milestone Feb 21, 2017
@michaelklishin
Copy link
Member Author

A lot of things have changed since rabbitmq/rabbitmq-management#236, so let's assume this is no longer relevant and see what long running test environments plus user feedback reveal.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants