You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by anuhbava <an...@aol.com> on 2011/03/18 05:18:31 UTC
network of broker stop forwarding messages without advisorySupport
enabled
I have setup network of brokers exactly as per this post of Bruce Snyder:
http://bsnyderblog.blogspot.com/2010/01/how-to-use-automatic-failover-in.html:
Broker 1:
Broker 2:
I have advisorySupport="false" in the broker tag of both the amq*.xml and
started all the brokers.
Then I started the consumer using command:
ant consumer -Durl=tcp://0.0.0.0:61616
and finally started producer using this command:
ant producer -Durl=tcp://0.0.0.0:61617
All the produced messaged then go in pending state on the broker running on
port 61617 and consumer connected on localhost:61616 broker never get the
messages.
Does the network of broker stop forwarding messages without advisorySupport
enabled? I thought that was fixed in recent release. (I'm using activemq
5.4.2 release).
--
View this message in context: http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3386261.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: network of broker stop forwarding messages without
advisorySupport enabled
Posted by anuhbava <an...@aol.com>.
Hi Gary,
Many many thanks for taking this issue up and providing a solution to this
problem.
I looked at: https://issues.apache.org/jira/browse/AMQ-3253 and attached
test case. I will download the snapshot release tomorrow ET to test my
scenario again.
Once again I really appreciate you spending your valuable time in fixing
this important issue which I hope will be part of AMQ 5.5 release.
cheers,
Anubhava
--
View this message in context: http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3426347.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: network of broker stop forwarding messages without
advisorySupport enabled
Posted by Gary Tully <ga...@gmail.com>.
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 <ga...@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 to the call
> to removeDestination in
> org.apache.activemq.broker.region.RegionBroker#purgeInactiveDestinations
>
> On 28 March 2011 23:18, anuhbava <an...@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:
>> "/>
>> Brokers ignored this directive for temporary destinations inclusions. It
>> seems staticallyIncludedDestinations only works for named queues and topics
>> 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
>> " advisoryForConsumed="false" advisoryForDelivery="false"
>> gcInactiveDestinations="true" inactiveTimoutBeforeGC="30000"/>
>>
>> in my destinationPolicy tag. However what I noticed is that even if producer
>> and consumer are killed but these newly created named topics are NOT deleted
>> 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 can
>> 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/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3413235.html
>> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>
>
>
> --
> http://blog.garytully.com
> http://fusesource.com
>
--
http://blog.garytully.com
http://fusesource.com
Re: network of broker stop forwarding messages without
advisorySupport enabled
Posted by Gary Tully <ga...@gmail.com>.
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 to the call
to removeDestination in
org.apache.activemq.broker.region.RegionBroker#purgeInactiveDestinations
On 28 March 2011 23:18, anuhbava <an...@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:
> "/>
> Brokers ignored this directive for temporary destinations inclusions. It
> seems staticallyIncludedDestinations only works for named queues and topics
> 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
> " advisoryForConsumed="false" advisoryForDelivery="false"
> gcInactiveDestinations="true" inactiveTimoutBeforeGC="30000"/>
>
> in my destinationPolicy tag. However what I noticed is that even if producer
> and consumer are killed but these newly created named topics are NOT deleted
> 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 can
> 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/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3413235.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
--
http://blog.garytully.com
http://fusesource.com
Re: network of broker stop forwarding messages without
advisorySupport enabled
Posted by anuhbava <an...@aol.com>.
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:
"/>
Brokers ignored this directive for temporary destinations inclusions. It
seems staticallyIncludedDestinations only works for named queues and topics
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
" advisoryForConsumed="false" advisoryForDelivery="false"
gcInactiveDestinations="true" inactiveTimoutBeforeGC="30000"/>
in my destinationPolicy tag. However what I noticed is that even if producer
and consumer are killed but these newly created named topics are NOT deleted
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 can
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/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3413235.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: network of broker stop forwarding messages without
advisorySupport enabled
Posted by Gary Tully <ga...@gmail.com>.
if you use:
session.createQueue("ID:ReplyDest.host-client-queue-" + new Date());
it will be a tempq, tied to a connection or possible to delete through
the javax.jms.TemporaryQueue#delete, and should still be usable from a
consumer.
Take a peek at the source:
http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/ActiveMQSession.java?view=markup
If you decide to use a real destination, check out
http://activemq.apache.org/delete-inactive-destinations.html
On 24 March 2011 22:11, anuhbava <an...@aol.com> wrote:
> Hi Gary,
>
> Thanks for your thoughtful response once again.
>
> I tried adding htis call in my code:
>
> connectionFactory.setClientIDPrefix("ID:ReplyDest.hostname");
>
>
> And then added this in activemq.xml in staticallyIncludedDestinations tag:
> "/>
>
>
> However I noticed that ActiveMQ ignored prefix string set from
> setClientIDPrefix call and still when I called
> session.createTemporaryQueue() it created temp queue names as
> "temp-queue://ID:host-40202-1301003416073-0:1:1"
>
> And because of that wildcard match failed inside
> staticallyIncludedDestinations.
>
> However when create a named queue like this:
> session.createQueue("ReplyDest.host-client-queue-" + new Date());
>
>
> And have this ReplyDest. configured in staticallyIncludedDestinations then
> request response flow through just fine, however since I'm putting Date() in
> queue name (to make it unique per instance) I see lots of those queues on
> AMQ console which I believe will be confusing to our operations folks. Is
> there anyway AMQ can clear these queues once there is no consumer?
>
> cheers,
> Anubhava
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3403957.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
--
http://blog.garytully.com
http://fusesource.com
Re: network of broker stop forwarding messages without
advisorySupport enabled
Posted by anuhbava <an...@aol.com>.
Hi Gary,
Thanks for your thoughtful response once again.
I tried adding htis call in my code:
connectionFactory.setClientIDPrefix("ID:ReplyDest.hostname");
And then added this in activemq.xml in staticallyIncludedDestinations tag:
"/>
However I noticed that ActiveMQ ignored prefix string set from
setClientIDPrefix call and still when I called
session.createTemporaryQueue() it created temp queue names as
"temp-queue://ID:host-40202-1301003416073-0:1:1"
And because of that wildcard match failed inside
staticallyIncludedDestinations.
However when create a named queue like this:
session.createQueue("ReplyDest.host-client-queue-" + new Date());
And have this ReplyDest. configured in staticallyIncludedDestinations then
request response flow through just fine, however since I'm putting Date() in
queue name (to make it unique per instance) I see lots of those queues on
AMQ console which I believe will be confusing to our operations folks. Is
there anyway AMQ can clear these queues once there is no consumer?
cheers,
Anubhava
--
View this message in context: http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3403957.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: network of broker stop forwarding messages without
advisorySupport enabled
Posted by Gary Tully <ga...@gmail.com>.
Interesting, the prefix "ID:" denotes a temp queue, it is generated
from the default connection id scheme. The consumer is doing a check
based on the connection id, it throws the exception because foo does
not match the auto generated connection id.
>From the code, it looks like there is a way around this,
org.apache.activemq.ActiveMQConnectionFactory#setClientIDPrefix
The default prefix is "ID:<hostName>, if you set it to
ID:ReplyDest.<hostname>, all of your connections and temp destinations
will match a wild card "ID:ReplyDest.>" for inclusion in a statically
included destination, but will also match their connection ids, so
creating consumers will work ok.
> on regular queues
When you use "temp.foo" you are creating a regular queue that is not
tied to a connection.
Correct, if the reply queue is shared, you will need to use a selector
based on correlation id.
Have a read of http://trenaman.blogspot.com/2009/01/message-selectors-and-activemq.html
for insights into the use of selectors.
On 22 March 2011 20:55, anuhbava <an...@aol.com> wrote:
> Gary,
>
> Many thanks for taking time to respond in detail on this issue.
>
> However when I attempted taking your approach # 1 (creating a named queue
> with name="ID:foo") I am getting this exception from createConsumer()
> method:
>
> [java] javax.jms.InvalidDestinationException: Cannot use a Temporary
> destination from another Connection
> [java] at
> org.apache.activemq.ActiveMQMessageConsumer.(ActiveMQMessageConsumer.java:189)
> [java] at
> org.apache.activemq.ActiveMQSession.createConsumer(ActiveMQSession.java:1116)
> [java] at
> org.apache.activemq.ActiveMQSession.createConsumer(ActiveMQSession.java:1060)
> [java] at
> org.apache.activemq.ActiveMQSession.createConsumer(ActiveMQSession.java:973)
> [java] at
> org.apache.activemq.ActiveMQSession.createConsumer(ActiveMQSession.java:946)
>
> When I name it something else like "temp.foo" it doesn't throw this
> exception however client doesn't get the responses back because that is not
> included in staticallyIncludedDestinations tag. so most likely it doesn't
> allow a queue name to start with "ID:".
>
> Regarding using regular queues for reply processing: Wouldn't we need to use
> selectors in that case to make sure response reaches back to the very same
> client instance of origin?
>
> Unfortunately the reason why I am chasing this issue is that ours is a large
> network with many dynamic producers/consumers causing creation of thousands
> of advisory topics on each broker instance.
>
> cheers,
> Anubhava
>
>
> Gary Tully wrote:
>>
>> correct, networking the dynamically created and named temp queues
>> require advisories.
>>
>> First note that advisories are typically fine, it is only in large
>> networks with many dynamic consumers that the advisory overhead is
>> significant.
>>
>> There are two possible workarounds for request reply when advisories
>> are disabled.
>> The first is to use named temp queues via
>> org.apache.activemq.ActiveMQSession#createQueue where names that start
>> with "ID:" are temporary.
>> The second is to use regular queues for reply processing. Using
>> regular queues gives the option to use persistent replies if you want
>> to deterministically process replies.
>> In both cases, the reply destination names will need to be included in
>> staticallyIncludedDestinations.
>>
>> It would be nice if it was possible to create a wildcard statically
>> included destination for all temp queues, but the current naming
>> convention will not facilitate that.
>> With s suitable prefix (say "REPLY.") for you named temp queue
>> or
>> reply queue, a wildcard staticallyIncludedDestinations should work
>> fine.
>>
>> On 22 March 2011 02:26, anuhbava <anubhava@aol.com> wrote:
>> > Gary,
>> >
>> > I ran into issues using advisorySupport="false" and
>> > staticallyIncludedDestinations.
>> >
>> > We use JMS for mostly request-response like described here:
>> >
>> http://activemq.apache.org/how-should-i-implement-request-response-with-jms.html
>> >
>> > We are using temporary queue on Producer side to be able to receive
>> response
>> > from Consumers and since staticallyIncludedDestinations cannot
>> include these
>> > temporary queue names in it therefore all the Producers are unable to
>> > receive responses back from clients when advisorySupport is disabled.
>> >
>> > I am coming to conclusion that for our scenario advisorySupport
>> cannot be
>> > turned off unless there is some other config trick I'm not aware of.
>> >
>> > Thanks,
>> > Anubhava
>> >
>> >
>> > On Mon, Mar 21, 2011 at 2:35 PM, Gary Tully [via ActiveMQ] <
>> > ml-node+3394397-1352398844-221362@n4.nabble.com> wrote:
>> >
>> >> thanks for closing the loop.
>> >>
>> >> On 21 March 2011 18:11, anuhbava <[hidden
>> email]<http://user/SendEmail.jtp?type=node&node=3394397&i=0&by-user=t>>
>> >> wrote:
>> >>
>> >> > Thank you very much Gary.
>> >> >
>> >> > Including this config:
>> >> >
>> >> > <staticallyIncludedDestinations>
>> >> > <queue physicalName="TEST.FOO"/>
>> >> > <queue physicalName="TEST.BAR"/>
>> >> > </staticallyIncludedDestinations>
>> >> >
>> >> > inside networkConnector tag did the trick.
>> >> >
>> >> > cheers,
>> >> > Anubhava
>> >> >
>> >> > On Mon, Mar 21, 2011 at 7:54 AM, Gary Tully [via ActiveMQ]
>> <
>> >> > [hidden
>> email]<http://user/SendEmail.jtp?type=node&node=3394397&i=1&by-user=t>>
>> >> wrote:
>> >> >
>> >> >> without advisories, you need to explicitly specify the
>> list of
>> >> >> statically included/excluded destinations for each
>> network connector.
>> >> >>
>> >> >> On 18 March 2011 22:42, anuhbava <[hidden email]<
>> >>
>> http://user/SendEmail.jtp?type=node&node=3393367&i=0&by-user=t>>
>> >>
>> >> >> wrote:
>> >> >>
>> >> >> > If you see my networkConnector tag in original post
>> you will notice
>> >> that
>> >> >> I
>> >> >> > don't have dynamic network brokers. Both of my
>> brokers have
>> >> >> > uri="static:(tcp://localhost:61616)" and
>> >> >> > uri="static:(tcp://localhost:61617)"
>> >> >> >
>> >> >> > Thanks.
>> >> >> >
>> >> >> > --
>> >> >> > View this message in context:
>> >> >>
>> >>
>> http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3388635.html<http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3388635.html?by-user=t><http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3388635.html%3Chttp://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3388635.html?by-user=t%3E&by-user=t>
>> >>
>> >> >>
>> >> >> > Sent from the ActiveMQ - User mailing list archive
>> at Nabble.com.
>> >> >> >
>> >> >>
>> >> >>
>> >> >>
>> >> >> --
>> >> >> http://blog.garytully.com
>> >> >> http://fusesource.com
>> >> >>
>> >> >>
>> >> >> ------------------------------
>> >> >> If you reply to this email, your message will be added
>> to the
>> >> discussion
>> >> >> below:
>> >> >>
>> >> >>
>> >>
>> http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3393367.html<http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3393367.html?by-user=t>
>> >> >> To unsubscribe from network of broker stop forwarding
>> messages without
>> >> >> advisorySupport enabled, click here<
>> >>
>> http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3386261&code=YW51YmhhdmFAYW9sLmNvbXwzMzg2MjYxfDE5NDQ4NzEwMjE=><http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3386261&code=YW51YmhhdmFAYW9sLmNvbXwzMzg2MjYxfDE5NDQ4NzEwMjE=%3E&by-user=t>.
>> >>
>> >> >>
>> >> >>
>> >> >
>> >> >
>> >> > --
>> >> > View this message in context:
>> >>
>> http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3394328.html<http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3394328.html?by-user=t>
>> >>
>> >> > Sent from the ActiveMQ - User mailing list archive at
>> Nabble.com.
>> >>
>> >>
>> >>
>> >> --
>> >> http://blog.garytully.com
>> >> http://fusesource.com
>> >>
>> >>
>> >> ------------------------------
>> >> If you reply to this email, your message will be added to the
>> discussion
>> >> below:
>> >>
>> >>
>> http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3394397.html
>> >> To unsubscribe from network of broker stop forwarding messages
>> without
>> >> advisorySupport enabled, click
>> here<http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3386261&code=YW51YmhhdmFAYW9sLmNvbXwzMzg2MjYxfDE5NDQ4NzEwMjE=>.
>> >>
>> >>
>> >
>> >
>> > --
>> > View this message in context:
>> http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3395331.html
>> > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>>
>>
>> --
>> http://blog.garytully.com
>> http://fusesource.com
>>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3397734.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
--
http://blog.garytully.com
http://fusesource.com
Re: network of broker stop forwarding messages without
advisorySupport enabled
Posted by anuhbava <an...@aol.com>.
Gary,
Many thanks for taking time to respond in detail on this issue.
However when I attempted taking your approach # 1 (creating a named queue
with name="ID:foo") I am getting this exception from createConsumer()
method:
[java] javax.jms.InvalidDestinationException: Cannot use a Temporary
destination from another Connection
[java] at
org.apache.activemq.ActiveMQMessageConsumer.(ActiveMQMessageConsumer.java:189)
[java] at
org.apache.activemq.ActiveMQSession.createConsumer(ActiveMQSession.java:1116)
[java] at
org.apache.activemq.ActiveMQSession.createConsumer(ActiveMQSession.java:1060)
[java] at
org.apache.activemq.ActiveMQSession.createConsumer(ActiveMQSession.java:973)
[java] at
org.apache.activemq.ActiveMQSession.createConsumer(ActiveMQSession.java:946)
When I name it something else like "temp.foo" it doesn't throw this
exception however client doesn't get the responses back because that is not
included in staticallyIncludedDestinations tag. so most likely it doesn't
allow a queue name to start with "ID:".
Regarding using regular queues for reply processing: Wouldn't we need to use
selectors in that case to make sure response reaches back to the very same
client instance of origin?
Unfortunately the reason why I am chasing this issue is that ours is a large
network with many dynamic producers/consumers causing creation of thousands
of advisory topics on each broker instance.
cheers,
Anubhava
Gary Tully wrote:
>
> correct, networking the dynamically created and named temp queues
> require advisories.
>
> First note that advisories are typically fine, it is only in large
> networks with many dynamic consumers that the advisory overhead is
> significant.
>
> There are two possible workarounds for request reply when advisories
> are disabled.
> The first is to use named temp queues via
> org.apache.activemq.ActiveMQSession#createQueue where names that start
> with "ID:" are temporary.
> The second is to use regular queues for reply processing. Using
> regular queues gives the option to use persistent replies if you want
> to deterministically process replies.
> In both cases, the reply destination names will need to be included in
> staticallyIncludedDestinations.
>
> It would be nice if it was possible to create a wildcard statically
> included destination for all temp queues, but the current naming
> convention will not facilitate that.
> With s suitable prefix (say "REPLY.") for you named temp queue
> or
> reply queue, a wildcard staticallyIncludedDestinations should work
> fine.
>
> On 22 March 2011 02:26, anuhbava <anubhava@aol.com> wrote:
> > Gary,
> >
> > I ran into issues using advisorySupport="false" and
> > staticallyIncludedDestinations.
> >
> > We use JMS for mostly request-response like described here:
> >
> http://activemq.apache.org/how-should-i-implement-request-response-with-jms.html
> >
> > We are using temporary queue on Producer side to be able to receive
> response
> > from Consumers and since staticallyIncludedDestinations cannot
> include these
> > temporary queue names in it therefore all the Producers are unable to
> > receive responses back from clients when advisorySupport is disabled.
> >
> > I am coming to conclusion that for our scenario advisorySupport
> cannot be
> > turned off unless there is some other config trick I'm not aware of.
> >
> > Thanks,
> > Anubhava
> >
> >
> > On Mon, Mar 21, 2011 at 2:35 PM, Gary Tully [via ActiveMQ] <
> > ml-node+3394397-1352398844-221362@n4.nabble.com> wrote:
> >
> >> thanks for closing the loop.
> >>
> >> On 21 March 2011 18:11, anuhbava <[hidden
> email]<http://user/SendEmail.jtp?type=node&node=3394397&i=0&by-user=t>>
> >> wrote:
> >>
> >> > Thank you very much Gary.
> >> >
> >> > Including this config:
> >> >
> >> > <staticallyIncludedDestinations>
> >> > <queue physicalName="TEST.FOO"/>
> >> > <queue physicalName="TEST.BAR"/>
> >> > </staticallyIncludedDestinations>
> >> >
> >> > inside networkConnector tag did the trick.
> >> >
> >> > cheers,
> >> > Anubhava
> >> >
> >> > On Mon, Mar 21, 2011 at 7:54 AM, Gary Tully [via ActiveMQ]
> <
> >> > [hidden
> email]<http://user/SendEmail.jtp?type=node&node=3394397&i=1&by-user=t>>
> >> wrote:
> >> >
> >> >> without advisories, you need to explicitly specify the
> list of
> >> >> statically included/excluded destinations for each
> network connector.
> >> >>
> >> >> On 18 March 2011 22:42, anuhbava <[hidden email]<
> >>
> http://user/SendEmail.jtp?type=node&node=3393367&i=0&by-user=t>>
> >>
> >> >> wrote:
> >> >>
> >> >> > If you see my networkConnector tag in original post
> you will notice
> >> that
> >> >> I
> >> >> > don't have dynamic network brokers. Both of my
> brokers have
> >> >> > uri="static:(tcp://localhost:61616)" and
> >> >> > uri="static:(tcp://localhost:61617)"
> >> >> >
> >> >> > Thanks.
> >> >> >
> >> >> > --
> >> >> > View this message in context:
> >> >>
> >>
> http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3388635.html<http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3388635.html?by-user=t><http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3388635.html%3Chttp://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3388635.html?by-user=t%3E&by-user=t>
> >>
> >> >>
> >> >> > Sent from the ActiveMQ - User mailing list archive
> at Nabble.com.
> >> >> >
> >> >>
> >> >>
> >> >>
> >> >> --
> >> >> http://blog.garytully.com
> >> >> http://fusesource.com
> >> >>
> >> >>
> >> >> ------------------------------
> >> >> If you reply to this email, your message will be added
> to the
> >> discussion
> >> >> below:
> >> >>
> >> >>
> >>
> http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3393367.html<http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3393367.html?by-user=t>
> >> >> To unsubscribe from network of broker stop forwarding
> messages without
> >> >> advisorySupport enabled, click here<
> >>
> http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3386261&code=YW51YmhhdmFAYW9sLmNvbXwzMzg2MjYxfDE5NDQ4NzEwMjE=><http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3386261&code=YW51YmhhdmFAYW9sLmNvbXwzMzg2MjYxfDE5NDQ4NzEwMjE=%3E&by-user=t>.
> >>
> >> >>
> >> >>
> >> >
> >> >
> >> > --
> >> > View this message in context:
> >>
> http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3394328.html<http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3394328.html?by-user=t>
> >>
> >> > Sent from the ActiveMQ - User mailing list archive at
> Nabble.com.
> >>
> >>
> >>
> >> --
> >> http://blog.garytully.com
> >> http://fusesource.com
> >>
> >>
> >> ------------------------------
> >> If you reply to this email, your message will be added to the
> discussion
> >> below:
> >>
> >>
> http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3394397.html
> >> To unsubscribe from network of broker stop forwarding messages
> without
> >> advisorySupport enabled, click
> here<http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3386261&code=YW51YmhhdmFAYW9sLmNvbXwzMzg2MjYxfDE5NDQ4NzEwMjE=>.
> >>
> >>
> >
> >
> > --
> > View this message in context:
> http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3395331.html
> > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
>
> --
> http://blog.garytully.com
> http://fusesource.com
>
--
View this message in context: http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3397734.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: network of broker stop forwarding messages without
advisorySupport enabled
Posted by Gary Tully <ga...@gmail.com>.
correct, networking the dynamically created and named temp queues
require advisories.
First note that advisories are typically fine, it is only in large
networks with many dynamic consumers that the advisory overhead is
significant.
There are two possible workarounds for request reply when advisories
are disabled.
The first is to use named temp queues via
org.apache.activemq.ActiveMQSession#createQueue where names that start
with "ID:" are temporary.
The second is to use regular queues for reply processing. Using
regular queues gives the option to use persistent replies if you want
to deterministically process replies.
In both cases, the reply destination names will need to be included in
staticallyIncludedDestinations.
It would be nice if it was possible to create a wildcard statically
included destination for all temp queues, but the current naming
convention will not facilitate that.
With s suitable prefix (say "REPLY.") for you named temp queue or
reply queue, a wildcard staticallyIncludedDestinations should work
fine.
On 22 March 2011 02:26, anuhbava <an...@aol.com> wrote:
> Gary,
>
> I ran into issues using advisorySupport="false" and
> staticallyIncludedDestinations.
>
> We use JMS for mostly request-response like described here:
> http://activemq.apache.org/how-should-i-implement-request-response-with-jms.html
>
> We are using temporary queue on Producer side to be able to receive response
> from Consumers and since staticallyIncludedDestinations cannot include these
> temporary queue names in it therefore all the Producers are unable to
> receive responses back from clients when advisorySupport is disabled.
>
> I am coming to conclusion that for our scenario advisorySupport cannot be
> turned off unless there is some other config trick I'm not aware of.
>
> Thanks,
> Anubhava
>
>
> On Mon, Mar 21, 2011 at 2:35 PM, Gary Tully [via ActiveMQ] <
> ml-node+3394397-1352398844-221362@n4.nabble.com> wrote:
>
>> thanks for closing the loop.
>>
>> On 21 March 2011 18:11, anuhbava <[hidden email]<http://user/SendEmail.jtp?type=node&node=3394397&i=0&by-user=t>>
>> wrote:
>>
>> > Thank you very much Gary.
>> >
>> > Including this config:
>> >
>> > <staticallyIncludedDestinations>
>> > <queue physicalName="TEST.FOO"/>
>> > <queue physicalName="TEST.BAR"/>
>> > </staticallyIncludedDestinations>
>> >
>> > inside networkConnector tag did the trick.
>> >
>> > cheers,
>> > Anubhava
>> >
>> > On Mon, Mar 21, 2011 at 7:54 AM, Gary Tully [via ActiveMQ] <
>> > [hidden email]<http://user/SendEmail.jtp?type=node&node=3394397&i=1&by-user=t>>
>> wrote:
>> >
>> >> without advisories, you need to explicitly specify the list of
>> >> statically included/excluded destinations for each network connector.
>> >>
>> >> On 18 March 2011 22:42, anuhbava <[hidden email]<
>> http://user/SendEmail.jtp?type=node&node=3393367&i=0&by-user=t>>
>>
>> >> wrote:
>> >>
>> >> > If you see my networkConnector tag in original post you will notice
>> that
>> >> I
>> >> > don't have dynamic network brokers. Both of my brokers have
>> >> > uri="static:(tcp://localhost:61616)" and
>> >> > uri="static:(tcp://localhost:61617)"
>> >> >
>> >> > Thanks.
>> >> >
>> >> > --
>> >> > View this message in context:
>> >>
>> http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3388635.html<http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3388635.html?by-user=t><http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3388635.html%3Chttp://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3388635.html?by-user=t%3E&by-user=t>
>>
>> >>
>> >> > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> http://blog.garytully.com
>> >> http://fusesource.com
>> >>
>> >>
>> >> ------------------------------
>> >> If you reply to this email, your message will be added to the
>> discussion
>> >> below:
>> >>
>> >>
>> http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3393367.html<http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3393367.html?by-user=t>
>> >> To unsubscribe from network of broker stop forwarding messages without
>> >> advisorySupport enabled, click here<
>> http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3386261&code=YW51YmhhdmFAYW9sLmNvbXwzMzg2MjYxfDE5NDQ4NzEwMjE=><http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3386261&code=YW51YmhhdmFAYW9sLmNvbXwzMzg2MjYxfDE5NDQ4NzEwMjE=%3E&by-user=t>.
>>
>> >>
>> >>
>> >
>> >
>> > --
>> > View this message in context:
>> http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3394328.html<http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3394328.html?by-user=t>
>>
>> > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>>
>>
>>
>> --
>> http://blog.garytully.com
>> http://fusesource.com
>>
>>
>> ------------------------------
>> If you reply to this email, your message will be added to the discussion
>> below:
>>
>> http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3394397.html
>> To unsubscribe from network of broker stop forwarding messages without
>> advisorySupport enabled, click here<http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3386261&code=YW51YmhhdmFAYW9sLmNvbXwzMzg2MjYxfDE5NDQ4NzEwMjE=>.
>>
>>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3395331.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
--
http://blog.garytully.com
http://fusesource.com
Re: network of broker stop forwarding messages without
advisorySupport enabled
Posted by anuhbava <an...@aol.com>.
Gary,
I ran into issues using advisorySupport="false" and
staticallyIncludedDestinations.
We use JMS for mostly request-response like described here:
http://activemq.apache.org/how-should-i-implement-request-response-with-jms.html
We are using temporary queue on Producer side to be able to receive response
from Consumers and since staticallyIncludedDestinations cannot include these
temporary queue names in it therefore all the Producers are unable to
receive responses back from clients when advisorySupport is disabled.
I am coming to conclusion that for our scenario advisorySupport cannot be
turned off unless there is some other config trick I'm not aware of.
Thanks,
Anubhava
On Mon, Mar 21, 2011 at 2:35 PM, Gary Tully [via ActiveMQ] <
ml-node+3394397-1352398844-221362@n4.nabble.com> wrote:
> thanks for closing the loop.
>
> On 21 March 2011 18:11, anuhbava <[hidden email]<http://user/SendEmail.jtp?type=node&node=3394397&i=0&by-user=t>>
> wrote:
>
> > Thank you very much Gary.
> >
> > Including this config:
> >
> > <staticallyIncludedDestinations>
> > <queue physicalName="TEST.FOO"/>
> > <queue physicalName="TEST.BAR"/>
> > </staticallyIncludedDestinations>
> >
> > inside networkConnector tag did the trick.
> >
> > cheers,
> > Anubhava
> >
> > On Mon, Mar 21, 2011 at 7:54 AM, Gary Tully [via ActiveMQ] <
> > [hidden email]<http://user/SendEmail.jtp?type=node&node=3394397&i=1&by-user=t>>
> wrote:
> >
> >> without advisories, you need to explicitly specify the list of
> >> statically included/excluded destinations for each network connector.
> >>
> >> On 18 March 2011 22:42, anuhbava <[hidden email]<
> http://user/SendEmail.jtp?type=node&node=3393367&i=0&by-user=t>>
>
> >> wrote:
> >>
> >> > If you see my networkConnector tag in original post you will notice
> that
> >> I
> >> > don't have dynamic network brokers. Both of my brokers have
> >> > uri="static:(tcp://localhost:61616)" and
> >> > uri="static:(tcp://localhost:61617)"
> >> >
> >> > Thanks.
> >> >
> >> > --
> >> > View this message in context:
> >>
> http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3388635.html<http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3388635.html?by-user=t><http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3388635.html%3Chttp://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3388635.html?by-user=t%3E&by-user=t>
>
> >>
> >> > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> >> >
> >>
> >>
> >>
> >> --
> >> http://blog.garytully.com
> >> http://fusesource.com
> >>
> >>
> >> ------------------------------
> >> If you reply to this email, your message will be added to the
> discussion
> >> below:
> >>
> >>
> http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3393367.html<http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3393367.html?by-user=t>
> >> To unsubscribe from network of broker stop forwarding messages without
> >> advisorySupport enabled, click here<
> http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3386261&code=YW51YmhhdmFAYW9sLmNvbXwzMzg2MjYxfDE5NDQ4NzEwMjE=><http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3386261&code=YW51YmhhdmFAYW9sLmNvbXwzMzg2MjYxfDE5NDQ4NzEwMjE=%3E&by-user=t>.
>
> >>
> >>
> >
> >
> > --
> > View this message in context:
> http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3394328.html<http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3394328.html?by-user=t>
>
> > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>
>
> --
> http://blog.garytully.com
> http://fusesource.com
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3394397.html
> To unsubscribe from network of broker stop forwarding messages without
> advisorySupport enabled, click here<http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3386261&code=YW51YmhhdmFAYW9sLmNvbXwzMzg2MjYxfDE5NDQ4NzEwMjE=>.
>
>
--
View this message in context: http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3395331.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: network of broker stop forwarding messages without
advisorySupport enabled
Posted by Gary Tully <ga...@gmail.com>.
thanks for closing the loop.
On 21 March 2011 18:11, anuhbava <an...@aol.com> wrote:
> Thank you very much Gary.
>
> Including this config:
>
> <staticallyIncludedDestinations>
> <queue physicalName="TEST.FOO"/>
> <queue physicalName="TEST.BAR"/>
> </staticallyIncludedDestinations>
>
> inside networkConnector tag did the trick.
>
> cheers,
> Anubhava
>
> On Mon, Mar 21, 2011 at 7:54 AM, Gary Tully [via ActiveMQ] <
> ml-node+3393367-14693935-221362@n4.nabble.com> wrote:
>
>> without advisories, you need to explicitly specify the list of
>> statically included/excluded destinations for each network connector.
>>
>> On 18 March 2011 22:42, anuhbava <[hidden email]<http://user/SendEmail.jtp?type=node&node=3393367&i=0&by-user=t>>
>> wrote:
>>
>> > If you see my networkConnector tag in original post you will notice that
>> I
>> > don't have dynamic network brokers. Both of my brokers have
>> > uri="static:(tcp://localhost:61616)" and
>> > uri="static:(tcp://localhost:61617)"
>> >
>> > Thanks.
>> >
>> > --
>> > View this message in context:
>> http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3388635.html<http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3388635.html?by-user=t>
>>
>> > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>> >
>>
>>
>>
>> --
>> http://blog.garytully.com
>> http://fusesource.com
>>
>>
>> ------------------------------
>> If you reply to this email, your message will be added to the discussion
>> below:
>>
>> http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3393367.html
>> To unsubscribe from network of broker stop forwarding messages without
>> advisorySupport enabled, click here<http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3386261&code=YW51YmhhdmFAYW9sLmNvbXwzMzg2MjYxfDE5NDQ4NzEwMjE=>.
>>
>>
>
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3394328.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
--
http://blog.garytully.com
http://fusesource.com
Re: network of broker stop forwarding messages without
advisorySupport enabled
Posted by anuhbava <an...@aol.com>.
Thank you very much Gary.
Including this config:
<staticallyIncludedDestinations>
<queue physicalName="TEST.FOO"/>
<queue physicalName="TEST.BAR"/>
</staticallyIncludedDestinations>
inside networkConnector tag did the trick.
cheers,
Anubhava
On Mon, Mar 21, 2011 at 7:54 AM, Gary Tully [via ActiveMQ] <
ml-node+3393367-14693935-221362@n4.nabble.com> wrote:
> without advisories, you need to explicitly specify the list of
> statically included/excluded destinations for each network connector.
>
> On 18 March 2011 22:42, anuhbava <[hidden email]<http://user/SendEmail.jtp?type=node&node=3393367&i=0&by-user=t>>
> wrote:
>
> > If you see my networkConnector tag in original post you will notice that
> I
> > don't have dynamic network brokers. Both of my brokers have
> > uri="static:(tcp://localhost:61616)" and
> > uri="static:(tcp://localhost:61617)"
> >
> > Thanks.
> >
> > --
> > View this message in context:
> http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3388635.html<http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3388635.html?by-user=t>
>
> > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
> >
>
>
>
> --
> http://blog.garytully.com
> http://fusesource.com
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3393367.html
> To unsubscribe from network of broker stop forwarding messages without
> advisorySupport enabled, click here<http://activemq.2283324.n4.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=3386261&code=YW51YmhhdmFAYW9sLmNvbXwzMzg2MjYxfDE5NDQ4NzEwMjE=>.
>
>
--
View this message in context: http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3394328.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: network of broker stop forwarding messages without
advisorySupport enabled
Posted by Gary Tully <ga...@gmail.com>.
without advisories, you need to explicitly specify the list of
statically included/excluded destinations for each network connector.
On 18 March 2011 22:42, anuhbava <an...@aol.com> wrote:
> If you see my networkConnector tag in original post you will notice that I
> don't have dynamic network brokers. Both of my brokers have
> uri="static:(tcp://localhost:61616)" and
> uri="static:(tcp://localhost:61617)"
>
> Thanks.
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3388635.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
--
http://blog.garytully.com
http://fusesource.com
RE: network of broker stop forwarding messages without
advisorySupport enabled
Posted by anuhbava <an...@aol.com>.
If you see my networkConnector tag in original post you will notice that I
don't have dynamic network brokers. Both of my brokers have
uri="static:(tcp://localhost:61616)" and
uri="static:(tcp://localhost:61617)"
Thanks.
--
View this message in context: http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3388635.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
RE: network of broker stop forwarding messages without
advisorySupport enabled
Posted by Michael La Budde <pa...@hotmail.com>.
I believe dynamic broker network topologies require advisorySupport to be enabled; as you can see here:
http://activemq.apache.org/advisory-message.html
> Date: Thu, 17 Mar 2011 21:18:31 -0700
> To: users@activemq.apache.org
> Subject: network of broker stop forwarding messages without advisorySupport enabled
>
> I have setup network of brokers exactly as per this post of Bruce Snyder:
> http://bsnyderblog.blogspot.com/2010/01/how-to-use-automatic-failover-in.html:
>
> Broker 1:
>
>
> Broker 2:
>
>
> I have advisorySupport="false" in the broker tag of both the amq*.xml and
> started all the brokers.
>
> Then I started the consumer using command:
> ant consumer -Durl=tcp://0.0.0.0:61616
> and finally started producer using this command:
> ant producer -Durl=tcp://0.0.0.0:61617
>
> All the produced messaged then go in pending state on the broker running on
> port 61617 and consumer connected on localhost:61616 broker never get the
> messages.
>
> Does the network of broker stop forwarding messages without advisorySupport
> enabled? I thought that was fixed in recent release. (I'm using activemq
> 5.4.2 release).
>
> --
> View this message in context: http://activemq.2283324.n4.nabble.com/network-of-broker-stop-forwarding-messages-without-advisorySupport-enabled-tp3386261p3386261.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.