On 03/26/2014 09:07 PM, Nitin Shah wrote:
I believe all messages get affected on the sender side. So nothing gets sent and therefore nothing gets received.
>
We have enabled heartbeats and yes we set the reconnect option always inbuilt. We set the connection option = "{reconnect: true, tcp_nodelay: true, heartbeat: 10}";What we see is that after the date and time get set on the module that has the Qpidd running, the messages stop getting sent. If one restarts the broker it recovers and send messages that may have been previously sent.
How are you determining that the messages aren't being sent? Are you monitoring the interaction over the wire?
When you say 'sent' here (as opposed to 'delivered', a distinction you made earlier), I'm assuming you mean they are not leaving the client. Is that true?
Can you verify whether the client is continually disconnecting due to heartbeat issues (changing the clock on the broker is I guess quite likely to cause issues with the timers detecting or sending heartbeats)? Unless your heartbeat interval is very low, I would still expect you to get some messages through on each reconnection, before you get disconnected.
Do your messages have any ttl set on them? --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
