RabbitMQ: don't derive your publishers and consumers from the same connection

That's something I learned this year.If you need to consume and publish messages, it feels natural to open a connection, and then create everything you need from it. It works, too.The problem starts if you stumble into a high memory alarm—which happens surprisingly easily, at around 60% usage. Rabbit then stops accepting messages (writes). However, the blocking happens on the connection, meaning your consumers (reads) will be also blocked if you used the same connection.This was non-fatal for us, with the symptom being a scheduled job failing to start. But in principle, if your consumers are blocked, the messages will never be drained, and the alarm will stay on forever.So: just make sure your consumers and publishers have their own connections.