publish msg encounting windows error code 10060(connection timeout) a long time period late after last publishing msg

[alanxz]

publish msg encounting windows error code 10060(connection timeout) a long time period late after last publishing msg

[alanxz]

With the exception of the immediate flag on BasicPublish, SimpleAmqpClient works with the RabbitMQ v3.0 broker. Using the immediate flag on the BasicPublish will result in a ConnectionException being thrown.

Googling the windows error code 10060 gets me this page: http://msdn.microsoft.com/en-us/library/windows/desktop/ms740668(v=vs.85).aspx Meaning the connection has timed out. Likely something between your client and the broker closes the TCP connection due to inactivity.

[chenyujian]

thank you for reply.i found configuration "heartbeat" in http://www.rabbitmq.com/configure.html.
it sets to 600(seconds) by default under 2.8.7 while rabbitmq 3.0 enable heartbeat by default.

[alanxz]

Yes, heartbeats are the correct thing to use to mitigate this problem.

However SimpleAmqpClient and rabbitmq-c do not support heartbeating.

[alanxz]

Actually thats a different kind of heartbeat than I was expecting (there's another type of heartbeating that AMQP supports that I thought you were talking about). I suspect this is new. I'll have to look into this.

[alanxz]

I got some clarification from the RabbitMQ guys as to these heartbeats: that configuration parameter is what the broker proposes to the client when negotiating the connection with the client. The client then has the final decision of how to setup heartbeats.

In the case of rabbitmq-c and SimpleAmqpClient we don't support heartbeats currently, and disable heart beats when connecting to the broker. So that configuration parameter on the broker will not have any effect on SimpleAmqpClient or rabbitmq-c

[chenyujian]

thank you for replying,i will trace this problem and make a continuously report.

[chenyujian]

i think i finally find the answer,there were firewalls between servers and clients.and the firewall will close the connection after a settled time.

[alanxz]

Thats a pretty common cause of network drops: firewalls and NATs, they like to disconnect inactive TCP connections after a certain amount of time.