- Newest
- Most votes
- Most comments
What you experienced is in fact expected, and our current RabbitMQ broker does not support modification of heartbeat value from the customer side (only consumer timeout). However, our MQ service team can help to modify the heartbeat value if you request with a specific number and provide the use case for justification. The default heartbeat value is 60 seconds. Hence, kindly raise a case to modify the heartbeat value for your RabbitMQ broker.
Hello,
You can specify the heartbeat value at your end by changing the configuration file named "rabbitmq.conf".
[+]. https://www.rabbitmq.com/configure.html#configuration-files
As you have mentioned, you can specify the value of heartbeat in the conifg file as heartbeat = 60. However, kindly confirm if your config file is in new file format or old format.
[+]. https://www.rabbitmq.com/configure.html#config-file-formats
Please find the below example Configuration File:
[+]. https://github.com/rabbitmq/rabbitmq-server/blob/main/deps/rabbit/docs/rabbitmq.conf.example
If you still observe the issue, you can raise a case to AWS support team and they will configure the heartbeat value for your Rabbit MQ broker.
Thanks
Your answer makes me think I'm probably missing something. My RabbitMQ is managed by AWS. As far as I can tell, I don't have direct access to the "rabbitmq.conf" file you mentioned. I must work through the configuration section that is exposed through AWS which I tried but failed (got an error that the heartbeat value added is unsupported). If I was managing my own RabbitMQ instance then this question was trivial. Even if I were to use a managed service such as "cloudamqp" then it was possible. But I can't find a way to do it through AWS management console / CLI. If I can somehow access my "rabbitmq.conf' of a managed AWS rabbitMMQ then please elaborate the steps on how to do so. Thanks
Relevant content
- asked 2 months ago
- asked 2 years ago
- asked 3 years ago
- asked 7 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
Thank you, I'll consider raising a case. Do you know if this is something that is expected to be supported through the configuration file at some point soon?