Reputation: 735
To communicate events in our cluster of tomcats we use rabbitmq and exchange fanout architecture. Every server is subscribed to exchange through temporary queue. Everything seems to work fine but time to time one or more consumers lose the connection and do not process message without leaving some useful information in logs a part of some broken pipe message.
Btw we use load balancer between rabbit cluster and our servers.
Any suggestion where could be the issue or what configuration should we review?
Upvotes: 1
Views: 776
Reputation: 22682
heartbeart
configuration.if you can, post the logs.
Upvotes: 1
Reputation: 10170
Don't auto acknowledge messages for start. In this way, if the consumer dies or whatever messages are re-queued. So, finish processing the message and then do explicit acknowledge.
Also with rabbit mq cluster, it's important to consider which queues you want mirrors etc.
Upvotes: 2