Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type;
  b=ZllHtWpr9rsijile1HK3q+PgzqPkASH4XRj0vjdxQxp8Z3430NoAeR4mVkcbWDnEamWAY5ctQGAAawEIg+0g76R/G0tI6QuGj4Erh4FX46728GunDvcK4aexc6SwgTJ5vlU0Rb6c8NcumJZk/HyFFUoKNLqNEHw25SDJ31aIlPc=;
Message-ID: <1347075915.33218.YahooMailClassic@web164904.mail.bf1.yahoo.com>
Date: Fri, 7 Sep 2012 20:45:15 -0700 (PDT)
From: Raja vedamoorthy <raja.vedamoorthy@yahoo.com>
Subject: Re: #AMQ-3353: Durable subscribers on durable topics don't receive
 messages after network disconnect
To: users@activemq.apache.org
In-Reply-To: 
 <CAH+vQmPjPePT3PL7zdLGwpVLaM_pxFNqzLGxs2ZC34HqSiKQbw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="-1611076590-75336929-1347075915=:33218"

---1611076590-75336929-1347075915=:33218
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Thank you Gary I will check.

--- On Fri, 9/7/12, Gary Tully <gary.tully@gmail.com> wrote:

From: Gary Tully <gary.tully@gmail.com>
Subject: Re: #AMQ-3353: Durable subscribers on durable topics don't receive=
 messages after network disconnect
To: users@activemq.apache.org
Date: Friday, September 7, 2012, 5:58 AM

There is reference to a unit test in that jira
(https://issues.apache.org/jira/browse/AMQ-3353), does it correctly
reflect your use case and the issue.

the test is:
https://issues.apache.org/jira/secure/attachment/12485386/DurableSubscriber=
WithNetworkDisconnectTest.java

If it does, then please reopen the issue and we will try and get to it for =
5.7

Note:
With dynamicOnly=3Dtrue, a durable sub is recreated by the bridge when
there is new demand, so when a remote durable sub registers again.
With dynamicOnly=3Dfalse, a durable sub is recreated on bridge startup,
so that messages flow to the remote broker irrespective of connected
consumers.


On 7 September 2012 11:13, Andreas Calvo <andreas.calvo@scytl.com> wrote:
> Wrong link: https://issues.apache.org/jira/browse/AMQ-3353
>
> El vie 07 sep 2012 11:57:12 CEST, Andreas Calvo escribi=F3:
>
>> Hi,
>> We are still affected by this issue.
>>
>> Taking a look at the code, it seems that upon undesired disconnection
>> and reconnection, all durable subscribers affected are lost.
>> Using JMX we're able to see how the NC is lost and not successfully
>> recreated.
>>
>> However, we've identified that even standalone brokers in a NoB are
>> affected by this issue, and did do not successfully reconnected to
>> each other.
>>
>> I'll try 5.7-SNAPSHOT, but we've been following this issue since 5.5
>> and now it's marked as resolved.
>>
>> Link: https://issues.apache.org/jira/browse/AMQ-3393
>>
>
> --
> Andreas Calvo G=F3mez
> Systems Engineer
> Scytl Secure Electronic Voting
> Pla=E7a Gal=B7la Placidia, 1-3, 1st floor =B7 08006 Barcelona
> Phone: + 34 934 230 324
> Fax:=A0=A0=A0+ 34 933 251 028
> http://www.scytl.com
>
> NOTICE: The information in this e-mail and in any of its attachments is
> confidential and intended solely for the attention and use of the named
> addressee(s). If you are not the intended recipient, any disclosure,
> copying,
> distribution or retaining of this message or any part of it, without the
> prior
> written consent of Scytl Secure Electronic Voting, SA is prohibited and
> may be
> unlawful. If you have received this in error, please contact the sender
> and
> delete the material from any computer.


--=20
http://fusesource.com
http://blog.garytully.com

---1611076590-75336929-1347075915=:33218--