【原创】使用 rabbitmq 中 heartbeat 功能可能会遇到的问题

最新推荐文章于 2023-02-09 23:55:16 发布
最新推荐文章于 2023-02-09 23:55:16 发布
阅读量569 收藏
点赞数
文章标签： 大数据 网络 python
原文链接：https://my.oschina.net/moooofly/blog/209823
版权

2019独角兽企业重金招聘Python工程师标准>>> hot3.png


【问题场景】
       客户端以 consumer 身份订阅到 rabbitmq server 上的 queue 上，客户端侧在 AMQP 协议的 Connection.Tune-Ok 信令中，设置 heartbeat 为 0，即要求服务器侧不启用 heartbeat 功能。服务器由于异常断电原因停止服务，结果客户端在短时间内无法感知到服务器端已经异常。

       刚刚出现这个问题时，就有测试人员和业务人员找到我这边说：经过改造的 rabbitmq-c 库可能存在重大 bug，服务器都关闭了，客户端怎么还那像什么都没发生一样继续工作着呢？听到这种疑问，我只问了两个问题就想到了答案：
  • 业务中是不是仅仅作为 consumer 运行的？
  • 服务器能否确认是因为异常断电导致停止服务？
  • 服务器和业务程序之间是否还有中间路由设备？
业务人员告诉我上述问题的答案分别是：是的、是的、没有。呵呵~~所以答案就已经确定了，你想到了么？

【问题分析】
这个问题可以从以下两个层面进行分析：
1. TCP 协议层面
      在此层面上讲，上述问题属于典型的 TCP 协议中的“半打开”问题，典型描述如下：
如果一方已经关闭或异常终止连接而另一方却还不知道，我们将这样的 TCP 连接称为半打开（Half-Open）的。任何一端的主机异常都可能导致发生这种情况。只要不打算在半打开连接上传输数据，仍处于连接状态的一方就不会检测另一方已经出现异常。
半打开连接的一个常见原因是，当客户主机突然掉电，而不是正常的结束客户应用程序后再关机。当然这里所谓的客户机并不是仅仅表示客户端。
      在这种情况发生时，作为 TCP 链路上只接收不发送数据的一方，只能依靠 TCP 协议本身的 keepalive 机制来检查链路是否处于正常状态。而通常 keepalive 机制下，需要大约 2 个小时时间才能触发。

2. AMQP 协议层面
      在此层面上讲，客户端由于是作为 consumer 订阅到 queue 上的，所以在该 AMQP/TCP 连接上客户端不会主动发送数据到 rabbitmq server 侧。当服务器由于异常断电停止服务后，consumer 不会接收到 AMQP 协议层面的终止信令，所以无法感知对端的情况。
      一种可能的解决办法是客户端侧在接收 N 次超时后，通过发送 AMQP 协议中的 Heartbeat 信令检测服务器端是否处于正常状态。


      在场景描述中说道“客户端侧在 AMQP 协议的 Connection.Tune-Ok 信令中，设置 heartbeat 为 0”，如果是将 heartbeat 设置为 30 会如何？答案是会同时触发服务器端和客户端的 heartbeat 功能，即服务器端会在一段时间内没有数据需要发送给客户端的情况下，发送一个心跳包给客户端；或者一段时间内没有收到任何数据，则判定为心跳超时，最终会关闭tcp连接（参考这里）。而客户端侧同样会触发对发送和接收 heartbeat 计时器的维护，分别用于判定发送和接收的超时情况。

在 amqp.h 头文件中可以看到目前 rabbitmq-c 对 heartbeat 的支持情况： 
* \param [in] heartbeat the number of seconds between heartbeat frame to 
 *             request of the broker. A value of 0 disables heartbeats. 
 *             Note rabbitmq-c only has partial support for hearts, as of 
 *             v0.4.0 heartbeats are only serviced during amqp_basic_publish(), 
 *             and amqp_simple_wait_frame()/amqp_simple_wait_frame_noblock()
目前 github 上的 rabbitmq-c 0.4.1 版本在 heartbeat 功能上的支持仅限上述 3 种 API。

      所以，需要解决的问题可以描述为： 客户端作为 consumer 订阅到服务器上的 queue 后，在无业务数据需要处理时，需要通过检测 Heartbeat 帧（信令）来判定服务器是否处于异常状态（换句话说，自己是否已经是“半打开”的 TCP 连接）。


【解决办法】
 建议的解决办法如下：
  • 客户端必须启用 heartbeat 功能（解决“半打开”问题的基础）； 
  • 客户端需要支持在发送空闲时，发送 heartbeat 的功能（因为目前客户端作为 producer 是长连接到 rabbitmq server 上的）； 
  • 客户端需要支持在接收空闲时，通过检测服务器端发送来的 heartbeat 帧来判定服务器端（或网络）是否处于正常状态（因为客户端作为 consumer 也是长连接到 rabbitmq server 上的，同时不会主动向 rabbitmq server 发送数据）。 

总结：
      只要客户端启用 heartbeat ，那么服务器就会在满足“一定条件”时，定时向客户端发送 heartbeat 信令，同时也会检测在空闲状态达到规定时间后是否收到 heartbeat 信令；而客户端侧作为 consumer 时，需要判定是否接收到数据（无论是常规数据还是 heartbeat 信令），若在一定时间内没有接收到数据，则认为当前链路可能存在问题。后续可以从业务上触发 consume 关系的重新建立。


      如下为使能了 heartbeat 功能后的打印输出：
【 作为 consumer 的情况下出现网络断开时的打印 】 
[warn] evsignal_init: socketpair: No error
drive_machine: [conn_init]  ---  TCP 3-way handshake start! --> [172.16.81.111:5672][s:53144]
drive_machine: [conn_connecting]  ---  connection timeout 1 time on socket(53144)
drive_machine: [conn_connected]  ---  connected on socket(53144)
53144: conn_state change   connected ==> snd_protocol_header
  --> Send Protocol.Header!
53144: conn_state change   snd_protocol_header ==> rcv_connection_start_method
[53144] drive_machine: wait for Connection.Start method another 10 seconds!!
  <-- Recv Connection.Start Method frame!
53144: conn_state change   rcv_connection_start_method ==> snd_connection_start_rsp_method
  --> Send Connection.Start-Ok Method frame!
53144: conn_state change   snd_connection_start_rsp_method ==> rcv_connection_tune_method
  <-- Recv Connection.Tune Method frame!
53144: conn_state change   rcv_connection_tune_method ==> snd_connection_tune_rsp_method
  --> Send Connection.Tune-Ok Method frame!
53144: conn_state change   snd_connection_tune_rsp_method ==> snd_connection_open_method
  --> Send Connection.Open Method frame!
53144: conn_state change   snd_connection_open_method ==> rcv_connection_open_rsp_method
  <-- Recv Connection.Open-Ok Method frame!
53144: conn_state change   rcv_connection_open_rsp_method ==> snd_channel_open_method
  --> Send Channel.Open Method frame!
53144: conn_state change   snd_channel_open_method ==> rcv_channel_open_rsp_method
[53144] drive_machine: wait for Channel.Open-Ok method another 10 seconds!!
  <-- Recv Channel.Open-Ok Method frame!
53144: conn_state change   rcv_channel_open_rsp_method ==> idle
[53144] drive_machine: [conn_idle]  ---  [CONSUMER]: Queue Declaring!
53144: conn_state change   idle ==> snd_queue_declare_method
  --> Send Queue.Declare Method frame!
53144: conn_state change   snd_queue_declare_method ==> rcv_queue_declare_rsp_method
[53144] drive_machine: wait for Queue.Declare-Ok method another 10 seconds!!
  <-- Recv Queue.Declare-Ok Method frame!
53144: conn_state change   rcv_queue_declare_rsp_method ==> idle
[53144] drive_machine: [conn_idle]  ---  [CONSUMER]: Queue Binding!
53144: conn_state change   idle ==> snd_queue_bind_method
  --> Send Queue.Bind Method frame!
53144: conn_state change   snd_queue_bind_method ==> rcv_queue_bind_rsp_method
[53144] drive_machine: wait for Queue.Bind method another 10 seconds!!
  <-- Recv Queue.Bind Method frame!
need to code something!
53144: conn_state change   rcv_queue_bind_rsp_method ==> idle
[53144] drive_machine: [conn_idle]  ---  [CONSUMER]: Basic QoS!
53144: conn_state change   idle ==> snd_basic_qos_method
  --> Send Basic.Qos Method frame!
53144: conn_state change   snd_basic_qos_method ==> rcv_basic_qos_rsp_method
  <-- Recv Queue.Qos-Ok Method frame!
need to code something!
53144: conn_state change   rcv_basic_qos_rsp_method ==> idle
[53144] drive_machine: [conn_idle]  ---  [CONSUMER]: Basic Consuming!
53144: conn_state change   idle ==> snd_basic_consume_method
  --> Send Basic.Consume Method frame!
53144: conn_state change   snd_basic_consume_method ==> rcv_basic_consume_rsp_method
  <-- Recv Basic.Consume-Ok Method frame!
need to code something!
53144: conn_state change   rcv_basic_consume_rsp_method ==> idle
[53144] drive_machine: [conn_idle]  ---  [CONSUMER]: Start waiting to recv!
53144: conn_state change   idle ==> rcv_basic_deliver_method
[53144] drive_machine: wait for Basic.Deliver method another 10 seconds!!
[53144] drive_machine: wait for Basic.Deliver method another 10 seconds!!
[53144] drive_machine: wait for Basic.Deliver method another 10 seconds!!
      ### Recv AMQP_FRAME_HEARTBEAT frame! ###
  <-- Recv Heartbeat frame!
53144: conn_state change   rcv_basic_deliver_method ==> snd_heartbeat
  --> Send Heartbeat frame!
53144: conn_state change   snd_heartbeat ==> rcv_basic_deliver_method
[53144] drive_machine: wait for Basic.Deliver method another 10 seconds!!
[53144] drive_machine: wait for Basic.Deliver method another 10 seconds!!
[53144] drive_machine: wait for Basic.Deliver method another 10 seconds!!
      ### Recv AMQP_FRAME_HEARTBEAT frame! ###
  <-- Recv Heartbeat frame!
53144: conn_state change   rcv_basic_deliver_method ==> snd_heartbeat
  --> Send Heartbeat frame!
53144: conn_state change   snd_heartbeat ==> rcv_basic_deliver_method
[53144] drive_machine: wait for Basic.Deliver method another 10 seconds!!
[53144] drive_machine: wait for Basic.Deliver method another 10 seconds!!
[53144] drive_machine: wait for Basic.Deliver method another 10 seconds!!
      ### Recv AMQP_FRAME_HEARTBEAT frame! ###
  <-- Recv Heartbeat frame!
53144: conn_state change   rcv_basic_deliver_method ==> snd_heartbeat
  --> Send Heartbeat frame!
53144: conn_state change   snd_heartbeat ==> rcv_basic_deliver_method
[53144] drive_machine: wait for Basic.Deliver method another 10 seconds!!
[53144] drive_machine: wait for Basic.Deliver method another 10 seconds!!
[53144] drive_machine: wait for Basic.Deliver method another 10 seconds!!
[53144] drive_machine: wait for Basic.Deliver method another 10 seconds!!
[53144] drive_machine: wait for Basic.Deliver method another 10 seconds!!
[53144] drive_machine: wait for Basic.Deliver method another 10 seconds!!
[53144] drive_machine: wait for Basic.Deliver method another 10 seconds!!
[53144] drive_machine: Recv nothing for 60s!
[53144] drive_machine: Maybe network broken or rabbitmq server fucked! Plz retry consuming!
53144: conn_state change   rcv_basic_deliver_method ==> close
[53144] drive_machine: [conn_close]  ---  Connection Disconnect!
### CB: Connection Disconnect!    Msg : [Connection Disconnect]



【 作为 producer 的情况下出现网络断开时的打印 】 
[warn] evsignal_init: socketpair: No error
drive_machine: [conn_init]  ---  TCP 3-way handshake start! --> [172.16.81.111:5672][s:12184]
drive_machine: [conn_connecting]  ---  connection timeout 1 time on socket(12184)
drive_machine: [conn_connected]  ---  connected on socket(12184)
12184: conn_state change   connected ==> snd_protocol_header
  --> Send Protocol.Header!
12184: conn_state change   snd_protocol_header ==> rcv_connection_start_method
  <-- Recv Connection.Start Method frame!
12184: conn_state change   rcv_connection_start_method ==> snd_connection_start_rsp_method
  --> Send Connection.Start-Ok Method frame!
12184: conn_state change   snd_connection_start_rsp_method ==> rcv_connection_tune_method
[12184] drive_machine: wait for Connection.Tune method another 10 seconds!!
  <-- Recv Connection.Tune Method frame!
12184: conn_state change   rcv_connection_tune_method ==> snd_connection_tune_rsp_method
  --> Send Connection.Tune-Ok Method frame!
12184: conn_state change   snd_connection_tune_rsp_method ==> snd_connection_open_method
  --> Send Connection.Open Method frame!
12184: conn_state change   snd_connection_open_method ==> rcv_connection_open_rsp_method
[12184] drive_machine: wait for Connection.Open-Ok method another 10 seconds!!
  <-- Recv Connection.Open-Ok Method frame!
12184: conn_state change   rcv_connection_open_rsp_method ==> snd_channel_open_method
  --> Send Channel.Open Method frame!
12184: conn_state change   snd_channel_open_method ==> rcv_channel_open_rsp_method
[12184] drive_machine: wait for Channel.Open-Ok method another 10 seconds!!
  <-- Recv Channel.Open-Ok Method frame!
12184: conn_state change   rcv_channel_open_rsp_method ==> snd_channel_confirm_select_method
  --> Send Confirm.Select Method frame!
12184: conn_state change   snd_channel_confirm_select_method ==> rcv_channel_confirm_select_rsp_method
  <-- Recv Confirm.Select-Ok Method frame!
Channel in Confirm Mode!
12184: conn_state change   rcv_channel_confirm_select_rsp_method ==> idle
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find msg to send!
12184: conn_state change   idle ==> snd_basic_publish_method
  --> Send Basic.Publish Method frame!
12184: conn_state change   snd_basic_publish_method ==> snd_basic_content_header
  --> Send Content-Header frame!
12184: conn_state change   snd_basic_content_header ==> snd_basic_content_body
  --> Send Content-Body frame!
12184: conn_state change   snd_basic_content_body ==> rcv_basic_ack_method
  <-- Recv Basic.Ack Method frame!
### CB: Publisher Confirm -- [Basic.Ack]  Delivery_Tag:[1]  multiple:[0]
12184: conn_state change   rcv_basic_ack_method ==> idle
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
12184: conn_state change   idle ==> snd_heartbeat
  --> Send Heartbeat frame!
12184: conn_state change   snd_heartbeat ==> idle
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
[12184] drive_machine: [conn_idle]  ---  [PRODUCER]: Find no msg to send! wait another 1 seconds
12184: conn_state change   idle ==> snd_heartbeat
[12184] drive_machine: Send Heartbeat failed! status = -9
12184: conn_state change   snd_heartbeat ==> close
[12184] drive_machine: [conn_close]  ---  Connection Disconnect!
### CB: Connection Disconnect!    Msg : [Connection Disconnect]






转载于:https://my.oschina.net/moooofly/blog/209823

weixin_33772645
关注
深入详解使用 RabbitMQ 过程中涉及到的多个细节问题（面试可用）
dvlinker的技术专栏
01-19 2万+
深入详解使用 RabbitMQ 过程中涉及到的多个细节问题，这些问题在面试时可能会被问到。
已解决com.rabbitmq.client.MissedHeartbeatException的正确解决方法，亲测有效！！！
最新发布
小明的Java问道之路
04-01 899
已解决com.rabbitmq.client.MissedHeartbeatException的正确解决方法，亲测有效！！！
rabbitmq heartbeat missing with heartbeat = N seconds原因总结
weixin_33963594的博客
03-06 1906
一直以来，在我们大规模使用rabbitmq的服务端应用中，都没有出现rabbitmq心跳超时而造成的的影响，反倒是在rabbitmq-cpp客户端出现过很多次该问题，一直以为客户端lib实现的问题（不过一直没有对源码长时间深究、主要是cpp是我们另外一个团队负责为主），由于是WAN应用，客户又不是专业的IT人员，该问题在我们重构了行情持久化的逻辑后有了大幅度的缓和，有几个月没有客户反馈该问题了。今...
rabbitmq——heartbeat
weixin_34347651的博客
01-23 455
2019独角兽企业重金招聘Python工程师标准>>> ...
PHP RabbitMQ的心跳问题
xdscode的博客
01-25 4140
环境 PHP7，Thinkphp5，php-amqp类库 场景描述 生产的消息队列，其消费者总是无故断开，基本在五天左右就会断开，但是程序端消费者的进程却仍在继续，并且没有捕获到任何异常。经过多次尝试，最终将问题定位在mq的心跳问题。因为我们数据中心的防火墙正在终止空闲连接 mq心跳 1.rabbitmq使用心跳机制来保持连接，在正常场景下，客户端期望通过发送心跳包来告知服务端自己存活。如果服务端连续两次发送心跳客户端均无回应，服务端会断开与客户端的连接。心跳间隔可在每次连接时设置。 2.因php是同步语言
RabbitMQ 在python下的一个坑 AMQPHeartbeatTimeout: No activity or too many missed heartbeats in the last 60
weixin_41789943的博客
05-09 2520
业务场景 : 这个场景下RabbitMQ 是作为 分布式消息队列 的作用出现的,这里用的是RabbitMQ 的Routing模式 ,这个就是在发布/订阅者 模式下 使用RoutingKey 去匹配多个队列,使得发布者可以根据实际的情况把消息发送到指定的一个或多个消费者队列中去 问题出现 的 异常 :pika.exceptions.AMQPHeartbeatTimeout: No activity or too many missed heartbeats in the last 60 sec...
使用rabbitmq解决超卖问题
11-28
当多个用户同时购买同一商品时，如果库存管理不当，可能会导致实际库存数量小于销售订单的数量，从而出现超卖现象。为了解决这个问题，我们可以利用消息队列，特别是RabbitMQ这样的中间件来实现分布式事务和异步处理...
tp6使用rabbitmq
09-22
通过以上步骤，你可以在TP6项目中有效地集成和使用RabbitMQ，实现高效、稳定的异步任务处理和系统间的通信。不过，实际开发中还可能涉及更多细节，如消息的序列化与反序列化、死信队列的使用、通道复用等，这些都...
利用RabbitMQ实现的聊天功能
07-15
比例user1 和user2 两个用户之前通过建立两个信道 1.当user1发送消息的时候，user1建立发送信道队列名称为：user1_to_user2，user2建立接收信道接收消费该队列的消息。 2.当user2发送消息的时候，user2建立发送信道...
rabbitmq的接口函数说明，api参数使用说明
05-10
rabbitmq的提供的各个接口函数使用说明，函数有 1、amqp_new_connection(声明一个新的connection) 2、amqp_open_socket(获取socket) 3、amqp_set_sockfd(将connection和sockfd进行绑定) 4、amqp_login(用于登录RabbitMQ server，主要目的为了进行权限管理) 5、amqp_channel_open(用于关联conn和channel) 6、amqp_exchange_declare(声明exchange) 7、amqp_queue_declare(声明queue) 8、amqp_queue_bind(声明binding，已经有的绑定直接返回，没有绑定的就会绑定) 9、amqp_basic_qos(控制预取消息数) 10、amqp_basic_consume(指定要接收的队列) 11、amqp_consume_message(接收数据) 12、int amqp_basic_ack(发送ask确认) 13、amqp_basic_reject(拒绝ask) 14、amqp_basic_publish(发布消息) 15、amqp_simple_wait_frame（回调等待服务器的结果返回） 16、amqp_basic_get（客户端主动获取服务器的下一条消息） 17、关闭 18、AE交换机的使用 19、死信交换机的使用
C++/QT 使用RabbitMQ
11-18
这个简单的应用展示了如何在QT+C++环境中使用RabbitMQ的基本功能。然而，实际项目中可能需要处理更复杂的需求，如错误处理、消息确认机制、多线程处理等。在深入学习RabbitMQ时，建议阅读官方文档，了解更高级的概念...
MQ13-源码分析-心跳参数设置
WenCoo的博客
02-09 535
在该函数中设置了心跳等相关参数的值。
RabbitMQ 心跳
i余数的博客
07-05 3240
定义了经过多长时间没有心跳，我们就认为RabbitMQ和客户端之间的连接不可达。这个值是在客户端和RabbitMQ服务端建立连接的时候通过商讨得出的。客户端必须配置有心跳。协商过程为：心跳间隔为服务端和客户端心跳检测时间间隔，一般为心跳超时的一半（心跳超时/2），即2次心跳检测失败便认为连接不可达。客户端和服务端的所有流量都会被记做为心跳。所以客户端可以仅在必要的时候，也就是没有其他流量的情况下发送心跳。也可以忽略其他流量，随时根据心跳间隔发送心跳。根据实践反馈，对于大多数环境来说，最佳设置范围是5-20秒
RabbitMQ修改默认端口和心跳
皇家大炮的博客
06-16 3853
RabbitMQ修改默认端口和心跳 项目安装部署RabbitMQ的时候，发现5672端口已经被占用。网上找的文章都是互相抄，不管用。经过大佬指导，修改成功了。现在记录下如何修改RabbitMQ修改端口和心跳。 找到rabbitMQ的安装目录 打开ebin文件夹，找到文件“rabbit.app” 以文本的形式打开。 修改tcp_listeners里面的端口号5672为5699 重启rabbitM...
MQ12-源码分析-amqp_consume_message函数
WenCoo的博客
02-09 928
这表示一个单调时钟的时间点。内部表示是ns，相对于单调时钟。有两个“特殊”值:- 0:表示“这一刻”，它的意思是投票0超时，或非阻塞选项UINT64_MAX:表示“在无穷大”，它的平均值轮询有一个无限超时原型。
RabbitMQ heartbeat原理
Nicholas的专栏
10-19 1624
RabbitMQ的heartbeat是用于客户端与RabbitMQ之间连接的存活状态检测，类似于tcp keepalives功能。本文将介绍RabbitMQ的heartbeat功能何时被创建以及如何检测连接存活状态。 1. RabbitMQ连接建立的协议流程 对于本文的研究主要聚焦到connection.tune和connection.tune-ok流程进行说明。 2.channel_max，frame_max，heartbeat参数值说明 客户端与RabbitMQ之间建立连接的流程图如上...
FISCO BCOS 节点启动初始化日志
软件工程小施同学 的专栏
08-26 828
info|2021-08-26 09:57:15.469850|[INITIALIZER][initGlobalConfig],enableCompress=true,compatibilityVersion=2.7.2,versionNumber=34013696,enableStat=false,chainId=1,useSMCrypto=false info|2021-08-26 09:57:15.469924|[INITIALIZER][SecureInitializer]loading priva
rabbitmq-c初探
cnhome的专栏
07-02 3948
RabbitMQ着实是个好东西，当然了也有对C语言client开发的支持。例子和文档少的可怜，只能去项目里去查看example来理解，简单整理了一些，以免走些弯路。主要是在版本对应上，这点就没Maven好了，只能对好类库和例子。 接下来我们简单看看需要的东东。 环境：Ubuntu 13.04 rabbitmq-server 默认的3.0.2-1 librabbitmq-dev 默认
使用rabbitmq会遇到什么问题
07-10
使用RabbitMQ可能会遇到以下一些常见问题： 1. 配置问题：配置RabbitMQ可能会变得复杂，特别是在集群或高可用性环境中。如果配置不正确，可能会导致性能问题或消息丢失。 2. 消息丢失：虽然RabbitMQ是一个可靠的...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值