RabbitMQ客户端是否需主动请求心跳超时？服务端默认值为60秒吗？

Hey there! Let's tackle your two questions about RabbitMQ heartbeats straight from the official docs:

Key Answers #

• Do clients have to actively request heartbeat timeouts?
  Absolutely. Clients must be configured to initiate a heartbeat request as part of the connection setup—this is how the client and server negotiate the final timeout value that both will use.

• Is the server's default heartbeat timeout 60 seconds?
  The official docs clarify that the heartbeat timeout is a negotiated value, not a fixed server-side setting. For RabbitMQ 3.0 and newer, the broker will automatically try to negotiate a heartbeat during connection (though clients can still reject this negotiation). While 60 seconds is a common default that many client libraries will propose, the actual timeout ends up being whatever both the client and server agree on during that handshake.

Official Documentation Context #

心跳超时值用于定义RabbitMQ及客户端库将对等TCP连接判定为不可达（中断）的时间周期。该值由客户端与RabbitMQ服务端在连接时协商确定。客户端必须配置为请求心跳。在RabbitMQ 3.0及更高版本中，代理端默认会尝试协商心跳（不过客户端仍可否决）。超时单位为秒……

A Quick Extra Tip #

Keep in mind that the heartbeat timeout dictates how long either the server or client will wait without receiving a heartbeat signal before marking the TCP connection as dead and closing it. While clients can opt out of heartbeats, this is generally not a good idea for production environments—it increases the risk of undetected broken connections hanging around.

内容的提问来源于stack exchange，提问作者natke