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 Sep 6, 2022. It is now read-only.
The RabbitMQ production server gets overloaded by new channels regularly and locks up because of the memory load. This seems to be caused by a bug in the postwait/node-amqp library that we are using. It seems to be creating a new AMQP channel each time a message is published, which obviously will cause serious problems.
Suggested solution
The node-amqp library has been marked as UNMAINTANED, so we need to look at moving to another library that is not buggy. There are multiple candidates:
Problem
The RabbitMQ production server gets overloaded by new channels regularly and locks up because of the memory load. This seems to be caused by a bug in the postwait/node-amqp library that we are using. It seems to be creating a new AMQP channel each time a message is published, which obviously will cause serious problems.
Suggested solution
The node-amqp library has been marked as UNMAINTANED, so we need to look at moving to another library that is not buggy. There are multiple candidates:
The text was updated successfully, but these errors were encountered: