Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of gary.tully@gmail.com designates
 209.85.216.43 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=BfnDNHiNtn2Dus4EqORyxuEUWdsfHzX+ObFJX7GNl0msRPQkuwY4JQwwOtZY1ANBZ0
         SGqIuTQ8Za4tlzzEvCnx4ABOEYwQr0xpZdF0DsEYivOyZRp/iYnTTzoU0U5Ga/EOkX+q
         chsYtSDU/UnU6/a/uNWZh+fqv5xq9gsMymDeU=
MIME-Version: 1.0
In-Reply-To: <AANLkTi=HEoYRbEsG1QvZYu47DR642aHOM+yQEraB4h3i@mail.gmail.com>
References: <1300488137874-3388635.post@n4.nabble.com>
	<AANLkTimpj775CCsT_iVCPFgf-H-2n1iY4PJJQPBvwcBT@mail.gmail.com>
	<AANLkTimY2BGViqXOWaE1d3ALUD2aYJ2j7Xs2ZQ8=bwd8@mail.gmail.com>
	<AANLkTikUwKF92Hz0hNy9DOyMN28egBZDmtRQvWHZbjSg@mail.gmail.com>
	<AANLkTi=N3LaQ4AWP8hK48OYAgWpSVodvjw4AN57j3+vz@mail.gmail.com>
	<AANLkTinc1PDi931s3do2H9M5WMxBWKU8KjEWmFOds7G6@mail.gmail.com>
	<1300827317566-3397734.post@n4.nabble.com>
	<AANLkTimt4nmEhQPLb9zuCOgdsQt4k4BHMD41=-VZAU5z@mail.gmail.com>
	<1301004692891-3403957.post@n4.nabble.com>
	<AANLkTimT3xwpywa1WXJCDnD=r9JSmCVjF=0d9rwRTnJA@mail.gmail.com>
	<1301350705390-3413235.post@n4.nabble.com>
	<AANLkTi=HEoYRbEsG1QvZYu47DR642aHOM+yQEraB4h3i@mail.gmail.com>
Date: Mon, 4 Apr 2011 19:00:42 +0100
Message-ID: <BANLkTiky62csfgQJSSFuOBepJ=+O1pSpBg@mail.gmail.com>
Subject: Re: network of broker stop forwarding messages without
 advisorySupport enabled
From: Gary Tully <gary.tully@gmail.com>
To: users@activemq.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Anubhava,
have a look at https://issues.apache.org/jira/browse/AMQ-3253 and the
associated test case. You can try the additional config with trunk or
tonight's snapshot. I will allow temp destinations to propagate a
network and allow the gc of destinations that have just network
consumers, which will work for your 'temp' non temporary destinations.

On 30 March 2011 19:00, Gary Tully <gary.tully@gmail.com> wrote:
> There is no easy answer with the current code. I am working on
> building in support for temp destinations across a network with no
> advisories, still some issues with ownership/lifecycle at the moment.
> Will let you know when I have something you can try out.
>
> In the short term, to delete your real destinations, if you can build
> your own broker from source, you could add a timeout > 0 =A0to the call
> to removeDestination in
> org.apache.activemq.broker.region.RegionBroker#purgeInactiveDestinations
>
> On 28 March 2011 23:18, anuhbava <anubhava@aol.com> wrote:
>> Hi Gary,
>>
>> Thanks for pointing the source code to me, its been a great help to try =
&
>> understand how AMQ code is behaving for these scenarios.
>>
>> Here is what I found so far:
>> 1. connectionFactory.setClientIDPrefix("ID:ReplyDest.host") and
>> connectionFactory.setClientID("ID:ReplyDest.host") calls are completely
>> ignored while creating a new temporary queue name.
>> 2. session.createQueue("ID:ReplyDest.host-client-queue-" + new Date());
>> throws exception as I mentioned earlier as well.
>> 3. Only hack I could find to alter the naming convention was this call:
>> ((ActiveMQConnection)
>> connection).getConnectionInfo().getConnectionId().setValue("ID:ReplyDest=
.");
>> 4. Using above trick will alter the naming convention of temporary
>> destinations as temp-queue://ID:ReplyDest.12334535345.1
>> 5. However when I added this in activemq.xml in
>> staticallyIncludedDestinations tag:
>> =A0 =A0"/>
>> =A0 =A0Brokers ignored this directive for temporary destinations inclusi=
ons. It
>> seems staticallyIncludedDestinations only works for named queues and top=
ics
>> but not for temp destinations.
>> 6. Now if I create regular destinations using
>> session.createTopic("ReplyDest.client-topic" + new Date()); and have
>> corresponding staticallyIncludedDestinations inclusions then my
>> request/responses flow without problems.
>> 7. As per your very nice suggestion I have now included
>> =A0" advisoryForConsumed=3D"false" advisoryForDelivery=3D"false"
>> gcInactiveDestinations=3D"true" inactiveTimoutBeforeGC=3D"30000"/>
>>
>> in my destinationPolicy tag. However what I noticed is that even if prod=
ucer
>> and consumer are killed but these newly created named topics are NOT del=
eted
>> until all but one the broker are shutdown. Which is somewhat unexpected
>> behavior and it may not work for us since at no time we are going to
>> shutdown our AMQ brokers in production, even though producer/consumers c=
an
>> be very dynamic and can start/stop many times. Do you have any other
>> suggestion for my case, one that can cleanup/remove these (temporary for=
 my
>> use case but not really temporary for AMQ) destinations without stopping=
 any
>> brokers?
>>
>> many thanks for your help so far,
>> Anubhava
>>
>>
>>
>>
>> --
>> View this message in context: http://activemq.2283324.n4.nabble.com/netw=
ork-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp33=
86261p3413235.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>
>
>
> --
> http://blog.garytully.com
> http://fusesource.com
>


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