🐛Webserver: exclusive/non-exclusive RabbitMQ consumers are deleting each other, and also probably replacing each other #5415
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What do these changes do?
After some Graylog analysis it came up that the following issue callback would happen quite often. It was found that both _rabbitmq_nonexclusive_queue_consumers and _rabbitmq_exclusive_queue_consumers were using the same
app[APP_RABBITMQ_CONSUMERS_KEY]
to store their respective consumers. E.G. on initialization the last one would replace the first one, and on deletion as well, thus the errors shown in Graylog. Not sure if this could also have some influence on the lost logs issues.Another issue was also identified when a user is logging out (also visible in e2e tests), and for this an additional log output was added.
Related issue/s
How to test
Dev Checklist
DevOps Checklist