Ok this is another instance of the similar problem. the "connection.Open()" (with "reconnect" option set to true) blocks the call and kicks off the retry process when its called for the first time. After that, if the connection is lost, it neither blocks the call nor kicks off the reconnect process. .Open() just returns and .IsOpen member is still showing true.
The only get around work I could find was to create a new instance of the Connection class with "reconnect" object. But this does not sound promising option since it means opening and closing connection for each message sent, in order to make sure the connection and reconnection availability. Ideas? Thanks, Sam On Wed, Dec 22, 2010 at 3:05 PM, qpid user 2 <[email protected]> wrote: > Thanks Chuck, > > The root cause of the issue I am facing is similar to the one mentioned in > the Jira you linked me to. I managed to make my sending procedure > indifferent from the status of the connection using a synchronization of the > messages and connection. My problem is that further on, options for > maintaining back the connection is limited. If the connection to the broker > is lost, ("reconnect" option is true), the connection.Open() call does not > return properly and the reconnection process get stocked. Also particularly > the .IsOpen member does not reflect correct connection status in some cases. > Is this a known issue? > > I am using Qpid 0.6. > > Thanks, > Sam > > P.S: I can further investigate and provide some suggestions. > > > > On Wed, Dec 22, 2010 at 2:47 PM, Chuck Rolke <[email protected]> wrote: > >> Hi Sam, >> >> Currently the connection returns no information callback about its >> connected/disconnected status besides error log messages and a final >> exception when the connection attempts fail. The connection.IsOpen member >> indicates True or False if the connection is actually connected. >> >> A similar issue is approached from a different angle in >> https://issues.apache.org/jira/browse/QPID-2978 "Disconnected operation >> is a pain", where the initial connection attempts hang the thread creating >> the connection. You may add a suggestion to that Jira or create a new one >> suggesting your improvement to the Messaging API. >> >> ----- Original Message ----- >> > From: "qpid user 2" <[email protected]> >> > To: "users" <[email protected]> >> > Sent: Wednesday, December 22, 2010 12:52:57 PM >> > Subject: C# Qpid Connection Lost >> > Hi guys, >> > >> > I have got a question on handling connection to the broker. I am using >> > C# >> > and the dotnet bindings libraries. I use "reconnect" option for my >> > Connection class. My question is that is there any sort of >> > notification >> > mechanism that I can handle when connection to broker is lost? some >> > sort of >> > callback or exception thrown when ever connection is lost. >> > >> > Help would be appreciated as usual. >> > >> > Thanks, >> > Sam >> >> --------------------------------------------------------------------- >> Apache Qpid - AMQP Messaging Implementation >> Project: http://qpid.apache.org >> Use/Interact: mailto:[email protected] >> >> >
