michaelklishin
commented
6 years ago Thank you for your time.
Team RabbitMQ uses GitHub issues for specific actionable items engineers can work on. This assumes two things:
- GitHub issues are not used for questions, investigations, root cause analysis, discussions of potential issues, etc (as defined by this team)
- We have a certain amount of information to work with
We get at least a dozen of questions through various venues every single day, often quite light on details. At that rate GitHub issues can very quickly turn into a something impossible to navigate and make sense of even for our team. Because of that questions, investigations, root cause analysis, discussions of potential features are all considered to be mailing list material by our team. Please post this to rabbitmq-users.
Getting all the details necessary to reproduce an issue, make a conclusion or even form a hypothesis about what's happening can take a fair amount of time. Our team is multiple orders of magnitude smaller than the RabbitMQ community. Please help others help you by providing a way to reproduce the behavior you're observing, or at least sharing as much relevant information as possible on the list:
- Server, client library and plugin (if applicable) versions used
- Server logs
- A code example or terminal transcript that can be used to reproduce
- Full exception stack traces (not a single line message)
rabbitmqctl status(and, if possible,rabbitmqctl environmentoutput)- Other relevant things about the environment and workload, e.g. a traffic capture
Feel free to edit out hostnames and other potentially sensitive information.
When/if we have enough details and evidence we'd be happy to file a new issue.
Thank you.
I use rabbitmq-web-stomp plugin for push message from server to mobile app, but I found channel total number keep growing, and memory occupation also keep growing. I think this is the channel not released.