Hi Gordon, I wanted to give you more information from the logs we saw. I am going to try this on the 0.26 release as well. I don't expect the problem to have gone away in the new release. I would like to know if you want other logs turned on to see more info. Let me know what if that helps.
Nitin LOGS below When TIME changed thru the CLI on the module that is running the broker , a time Change time of a minute through CLI saw the following errors on primary Module ( running the broker ) but no errors on the other modules. 2014-03-27T10:38:34.919457-04:00 scm1 qpidd[28177]: 2014-03-27 10:38:34 [Protocol] error Connection qpid.172.16.0.4:5672-172.16.0.4:37806 timed out: closing 2014-03-27T10:38:34.928981-04:00 scm1 qpidd[28177]: 2014-03-27 10:38:34 [Protocol] error Connection qpid.172.16.0.4:5672-172.16.0.4:37807 timed out: closing 2014-03-27T10:38:34.929669-04:00 scm1 qpidd[28177]: 2014-03-27 10:38:34 [Protocol] error Connection qpid.172.16.0.4:5672-172.16.0.4:37810 timed out: closing 2014-03-27T10:38:34.930076-04:00 scm1 qpidd[28177]: 2014-03-27 10:38:34 [Protocol] error Connection qpid.172.16.0.4:5672-172.16.0.4:37808 timed out: closing 2014-03-27T10:38:34.930490-04:00 scm1 qpidd[28177]: 2014-03-27 10:38:34 [Protocol] error Connection qpid.172.16.0.4:5672-172.16.0.4:37809 timed out: closing 2014-03-27T10:38:34.930855-04:00 scm1 qpidd[28177]: 2014-03-27 10:38:34 [Protocol] error Connection qpid.172.16.0.4:5672-172.16.0.4:37811 timed out: closing 2014-03-27T10:38:34.931833-04:00 scm1 qpidd[28177]: 2014-03-27 10:38:34 [Protocol] error Connection qpid.172.16.0.4:5672-172.16.0.4:37812 timed out: closing 2014-03-27T10:38:34.932094-04:00 scm1 qpidd[28177]: 2014-03-27 10:38:34 [Protocol] error Connection qpid.172.16.0.4:5672-172.16.0.4:37813 timed out: closing 2014-03-27T10:38:34.932484-04:00 scm1 qpidd[28177]: 2014-03-27 10:38:34 [Protocol] error Connection qpid.172.16.0.4:5672-172.16.0.4:37814 timed out: closing Changed time by 10 minutes Saw the same errors as above on primary SCM ( the one running the broker )and saw following errors on payload modules 2014-03-27T10:40:54.413172-04:00 pld0103 TransceiverAgent[9469]: [1.E.Mbus]: qpid connection failed exception 2014-03-27T10:40:54.435011-04:00 pld0103 DigiAgentSim[9467]: [1.E.Mbus]: qpid connection failed exception -----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. 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? --------------------------------------------------------------------- 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]
