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
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 wi
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 de
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
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/activem
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
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 aro
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
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 adviso
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 recei
thanks for closing the loop.
On 21 March 2011 18:11, anuhbava wrote:
> Thank you very much Gary.
>
> Including this config:
>
>
>
>
>
>
> inside networkConnector tag did the trick.
>
> cheers,
> Anubhava
>
> On Mon, Mar 21, 2011 at 7:54 AM, Gary Tully [via ActiveMQ] <
> ml-nod
Thank you very much Gary.
Including this config:
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-221...@n4.nabble.com> wrote:
> without advisories, you need to explicitly sp
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 wrote:
> If you see my networkConnector tag in original post you will notice that I
> don't have dynamic network brokers. Both of m
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 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 advisor
15 matches
Mail list logo
