Hi Gary,
Many thanks for all your help in the past for ActivemQ related issues. But I
have one more :)
I am facing exactly same issue on my end as mentioned in this thread:
http://activemq.2283324.n4.nabble.com/jira-Created-AMQ-3336-Temporary-Destination-errors-on-H-A-failover-in-broker-network-
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
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 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
d 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 staticallyI
orySupport 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-221...@n4.nabble.com> wrote:
> thanks for closing the loop.
>
> On 21 March 2011 18:
xplicitly 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 n
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/netw
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 co
