qpid-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From qpid user 2 <qpid.use...@gmail.com>
Subject Re: C# Qpid Connection Lost
Date Fri, 31 Dec 2010 11:42:36 GMT
Just to refreshing points on to the following thread, when the reconnect
option is disabled, after the first connection establishes, if the
connection is lost, no notification is sent across, e.g. an exception or
call back. And the reconnection itself does not update the IsOpen property
when it establishes the connection from a lost one.

I know the heartbeat option is supposed to take care of the time interval
between connection check (and possibly updating the value of IsOpen
property). But this option has the drawback that during the heartbeat
period, there would be no way to check for the status of the connection.

Help and thoughts would be appreciated.


On Wed, Dec 29, 2010 at 4:08 PM, qpid user 2 <qpid.user.2@gmail.com> wrote:

> The reconnect option IS available in Qpid 0.6, as well as
> reconnect_interval and reconnect_timeout. However the heartbeat option is
> not available. and as I mentioned, the reconnection works only for the first
> time trying to connect, and not when the connection is lost after the the
> connection is established the first time.
> Thanks,
> Sam
> On Thu, Dec 23, 2010 at 2:41 PM, Ted Ross <tross@redhat.com> wrote:
>> On 12/22/2010 03:05 PM, qpid user 2 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.
>> The .NET bindings with the reconnect option were not available in Qpid
>> 0.6.
>> -Ted
>> ---------------------------------------------------------------------
>> Apache Qpid - AMQP Messaging Implementation
>> Project:      http://qpid.apache.org
>> Use/Interact: mailto:users-subscribe@qpid.apache.org

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message