You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by Gregg Saffell <gs...@ilstechnology.com> on 2015/08/03 19:47:27 UTC

Re: Reply message not forwarded across temporary bridged destination

Thanks for the reply but I still not clear on what I will put in my
activemq.xml file for the physicalName attribute of the tempQueue element.
What is in the string that replyQWildcard.getPhysicalName() returns?

I'm not sure why you think I would need two non-duplex networkConnectors but
I have a limitation in that the hub can connect to the spokes but not the
other way around. I'm therefore limited to a duplex networkConnector that is
created on the hub. 

I was thinking I could do it like this : 

      <networkConnector name="acme" uri="static:(ssl://server.acme.com...
duplex="true">
        <staticallyIncludedDestinations>
          <queue physicalName="TO_SPOKE.SERVER_ACME_COM.ASYNC_MSGS"/>
          <queue physicalName="TO_HUB.ASYNC_MSGS"/>
          <queue physicalName="TO_HUB.SYNC_REQ"/>
        </staticallyIncludedDestinations>
      </networkConnector>

      <dynamicallyIncludedDestinations>
           <queue physicalName="SHOULD_NEVER_EXIST"/>
      </dynamicallyIncludedDestinations>

In case it isn't obvious... the spoke sends the req/reply message to the hub
via the TO_HUB.SYNC_REQ queue. The only consumers on that queue (on the
spoke) are for the hub's networkConnector thus ensuring the messages placed
in that queue go to the hub for processing. The queue SHOULD_NEVER_EXIST
should never exist thus ensuring that no dynamically created queues are
shared.

What I would need then is a policy that allows the dynamically created
tempQueue that is created on the spoke when it puts a req/reply message in
TO_HUB.SYNC_REQ to be shared between the hub and that one spoke.

Maybe the policy will also render the <dynamicallyIncludedDestinations>
entry above unnecessary. That would be even better.

Thanks again!    







--
View this message in context: http://activemq.2283324.n4.nabble.com/Reply-message-not-forwarded-across-temporary-bridged-destination-tp4688578p4700339.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Re: Reply message not forwarded across temporary bridged destination

Posted by Tim Bain <tb...@alumni.duke.edu>.
As described by azdvorak on 12/9/2014 and documented on
http://activemq.apache.org/networks-of-brokers.html, the
bridgeTempDestinations configuration option is the proper way to
dynamically bridge temp destinations.

The two previous posters were both trying to bridge temp destinations
statically whereas you're trying to do it dynamically (the simpler
scenario), so the behavior you're seeing is not related to the questions
they were asking. So if something's not working, please follow up in one of
the three other threads you currently have open, or start a new thread if
there's a reason your questions should not go into your existing threads;
please do not continue to hijack this unrelated thread.

Tim

On Sat, Feb 24, 2018 at 4:57 PM, Rajesh Malla <ma...@gmail.com> wrote:

> Can anybody please provide reply for this. What pattern we need to use ?
>
>
>
> --
> Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-
> f2341805.html
>

Re: Reply message not forwarded across temporary bridged destination

Posted by Rajesh Malla <ma...@gmail.com>.
Can anybody please provide reply for this. What pattern we need to use ?



--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: Reply message not forwarded across temporary bridged destination

Posted by Rajesh Malla <ma...@gmail.com>.
Hello

We are having similar problem in request/reply pattern with temp queue. we
are not getting response when we are using addDynamicallyIncludedDestination
on networkconnector with some queues.

so can anybody suggest what pattern to use if we are using in java code. for
example :

NetworkConnector networkConnector = new DiscoveryNetworkConnector(uri);
networkConnector.addDynamicallyIncludedDestination(???)

we tried with new ActiveMQQueue(">")  but still not able to receive response
messages. Please help us.



--
Sent from: http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html

Re: Reply message not forwarded across temporary bridged destination

Posted by Gregg Saffell <gs...@ilstechnology.com>.
Never mind my most recent questions. I found a post where Gary Tully said
that advisory messages should be turned off when the number of brokers gets
into the double digits. We are approaching triple digits so we've decided to
just remove the use of temp queues with request/reply messages and turn off
advisory messages entirely.




--
View this message in context: http://activemq.2283324.n4.nabble.com/Reply-message-not-forwarded-across-temporary-bridged-destination-tp4688578p4700901.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.