RE: Qpid and Behavior on NTP time change

2014-04-09 Thread Nitin Shah
__ From: Gordon Sim [g...@redhat.com] Sent: Tuesday, April 08, 2014 4:50 AM To: dev@qpid.apache.org Subject: Re: Qpid and Behavior on NTP time change On 04/03/2014 09:50 PM, Nitin Shah wrote: > Gordon , Qpid team, > > Can you explain what that means. Changing the time will confuse the br

Re: Qpid and Behavior on NTP time change

2014-04-08 Thread Gordon Sim
On 04/03/2014 09:50 PM, Nitin Shah wrote: Gordon , Qpid team, Can you explain what that means. Changing the time will confuse the broker (and the c++ client) in their processing of heartbeats (since they use the time to determine when heartbeats should be sent and when they should be expecte

Re: Qpid and Behavior on NTP time change

2014-04-03 Thread Ted Ross
ginal Message- From: Gordon Sim [mailto:g...@redhat.com] Sent: Friday, March 28, 2014 11:41 AM To: dev@qpid.apache.org Subject: Re: Qpid and Behavior on NTP time change On 03/28/2014 02:50 PM, Nitin Shah wrote: When TIME changed thru the CLI on the module that is running the broker , a time

RE: Qpid and Behavior on NTP time change

2014-04-03 Thread Nitin Shah
be transferred. The time change is a jump and could be 15 minutes. Let me know if I can provide any further information. Thanks Nitin -Original Message- From: Gordon Sim [mailto:g...@redhat.com] Sent: Friday, March 28, 2014 11:41 AM To: dev@qpid.apache.org Subject: Re: Qpid and

RE: Qpid and Behavior on NTP time change

2014-03-28 Thread Nitin Shah
lto:g...@redhat.com] Sent: Wednesday, March 26, 2014 12:52 PM To: dev@qpid.apache.org 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

Re: Qpid and Behavior on NTP time change

2014-03-28 Thread Gordon Sim
On 03/28/2014 02:50 PM, Nitin Shah wrote: 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

Re: Qpid and Behavior on NTP time change

2014-03-27 Thread Gordon Sim
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_n

RE: Qpid and Behavior on NTP time change

2014-03-26 Thread Nitin Shah
My responses embedded below -Original Message- From: Gordon Sim [mailto:g...@redhat.com] Sent: Wednesday, March 26, 2014 12:52 PM To: dev@qpid.apache.org Subject: Re: Qpid and Behavior on NTP time change On 03/25/2014 06:55 PM, Nitin Shah wrote: > Hi , > > I have talked to thi

Re: Qpid and Behavior on NTP time change

2014-03-26 Thread Gordon Sim
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++.

Re: Qpid and Behavior on NTP time change

2014-03-26 Thread Andrew Stitcher
On Wed, 2014-03-26 at 11:34 -0400, Nitin Shah wrote: > We have been looking at the code and wondered if CLOCK_MONOTONIC can be used. > Qpid uses AbsTime everywhere. > Now it is possible that Qpid has decided to use REALTIME because there is the > need for a real time clock between machines run

RE: Qpid and Behavior on NTP time change

2014-03-26 Thread Nitin Shah
: Andrew Stitcher [mailto:astitc...@redhat.com] Sent: Wednesday, March 26, 2014 11:20 AM To: dev@qpid.apache.org Cc: Gordon Sim (g...@redhat.com); Atif Faheem; Tony Hart; Lynne Morrison Subject: Re: Qpid and Behavior on NTP time change On Wed, 2014-03-26 at 10:56 -0400, Nitin Shah wrote: > Hi And

RE: Qpid and Behavior on NTP time change

2014-03-26 Thread Nitin Shah
ynne Morrison Subject: RE: Qpid and Behavior on NTP time change Hi Andrew and Qpid team, We are really blocked by this issue and need to have a conversation going about the options to resolve our issue. I am adding others from our team so they can chime in if necessary. Thanks Nitin -Orig

Re: Qpid and Behavior on NTP time change

2014-03-26 Thread Andrew Stitcher
On Wed, 2014-03-26 at 10:56 -0400, Nitin Shah wrote: > Hi Andrew and Qpid team, > > We are really blocked by this issue and need to have a conversation going > about the options to resolve our issue. I am adding others from our team so > they can chime in if necessary. As I said in my initial r

RE: Qpid and Behavior on NTP time change

2014-03-26 Thread Nitin Shah
, 2014 4:44 PM To: Andrew Stitcher; dev@qpid.apache.org Cc: Gordon Sim (g...@redhat.com); Nitin Shah Subject: RE: Qpid and Behavior on NTP time change Andrew, We have the NTP running on all the cards and I think I misled you on that. However, we have a CLI that allows the user to set the time and

RE: Qpid and Behavior on NTP time change

2014-03-25 Thread Nitin Shah
that seems to cause the lock up. If NTP does it , that seems fine. Nitin -Original Message- From: Andrew Stitcher [mailto:astitc...@redhat.com] Sent: Tuesday, March 25, 2014 4:26 PM To: dev@qpid.apache.org Cc: Nitin Shah; Gordon Sim (g...@redhat.com) Subject: Re: Qpid and Behavior on NTP

Re: Qpid and Behavior on NTP time change

2014-03-25 Thread Andrew Stitcher
On Tue, 2014-03-25 at 14:55 -0400, 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 >

Qpid and Behavior on NTP time change

2014-03-25 Thread Nitin Shah
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 synchroniz