My responses embedded below
-----Original Message-----
From: Gordon Sim [mailto:[email protected]]
Sent: Wednesday, March 26, 2014 12:52 PM
To: [email protected]
Subject: Re: Qpid and Behavior on NTP time change
On 03/25/2014 06:55 PM, Nitin Shah wrote:
> Hi ,
>
> I have talked to this mailing list before as we are users of QPID in our
> distributed system. Our architecture has multiple modules connected together
> via a backplane Ethernet link. We use QPID version 0.24 release both broker
> and clients are C++.
>
> Recently we have been trying to synchronize time across all modules using
> the messaging mechanism. However, we are seeing the following problem and the
> sequence of operation is this:
>
>
> 1. The module running the Qpid Broker receives an time update from a
> NTP server. It updates the local date/time and hwclock ( we are on Linux )
> and sends a message that suggests all the other modules to update their
> clocks accordingly using the messaging in Qpid.
>
> 2. These messages are not getting sent or are not getting delivered to
> the other modules until we kill and restart the broker. It seems this must be
> as a result of the time change that has happened where the broker is running.
Is it only these messages with which you are having problems, or are all
messages through qpidd affected? Try to determine whether they are not getting
sent or are not getting delivered as those are obviously two different issues.
You can use wireshark for example to examine the interactions.
Nitin:: I believe all messages get affected on the sender side. So nothing gets
sent and therefore nothing gets received.
Are you using heartbeats on your connections, and are you using any reconnect
logic (inbuilt or application defined)? Are there errors in the qpidd logs?
Nitin:: 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected] For additional
commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
