I use jndi.properties to describe jndi queue and physical queue.
When I describe a local queue I have no problem.
But I search in the documentation of jndi.properties how describe the
physical queue of an another broker.
I try this configuration but it doesn't work
My local broker has the name M1BROKER - my remote broker has the name
M2BROKER
The physical queue on M2BROKER is Q1
I try this form for jndi.properties to the JMC client whic send message to
M2BROKER/Q1 via the local connection with M1BROKER
queue.RQ1 = M2BROKER/Q1
When I put message to RQ1, the "transmission queue" M2BROKER/Q1 has a good
curdepth but my listener waiting on Q1 (M2BROKER) doesn't receive message
from M1BROKER.
M1BROKER and M2BROKER are normally linked
jndi.properties on M1BROKER
# Client M1BROKER sur 61616
java.naming.factory.initial =
org.apache.activemq.jndi.ActiveMQInitialContextFactory
# use the following property to configure the default connector
java.naming.provider.url = tcp://172.16.177.252:61616
# use the following property to specify the JNDI name the connection factory
# should appear as.
connectionFactoryNames = M1BROKER
# register some queues in JNDI using the form
# queue.[jndiName] = [physicalName]
queue.RQ1 = M2BROKER/Q1
queue.LOCAL = LOCAL
# register some topics in JNDI using the form
# topic.[jndiName] = [physicalName]
#topic.MyTopic = example.MyTopic
jndi.properties on M2BROKER
# pour M2BROKER
java.naming.factory.initial =
org.apache.activemq.jndi.ActiveMQInitialContextFactory
# use the following property to configure the default connector
java.naming.provider.url = tcp://172.16.177.252:62616
# use the following property to specify the JNDI name the connection factory
# should appear as.
connectionFactoryNames = M2BROKER
# register some queues in JNDI using the form
# queue.[jndiName] = [physicalName]
queue.Q1 = Q1
# register some topics in JNDI using the form
# topic.[jndiName] = [physicalName]
#topic.MyTopic = example.MyTopic
Log on M1BROKER
2009-03-13 11:16:20,712 [vm://M1BROKER#8] INFO DemandForwardingBridge
- Network connection between vm://M1BROKER#8 and
tcp://ITEM-57186.dhcp.ancy.fr.sopra/172.16.177.252:62616(M2BROKER) has been
established.
2009-03-13 11:19:48,070 [6.177.252:62616] DEBUG AbstractRegion
- Adding destination: topic://ActiveMQ.Advisory.Consumer.Queue.Q1
2009-03-13 11:19:48,070 [6.177.252:62616] DEBUG DemandForwardingBridge
- M1BROKER Forwarding sub on vm://M1BROKER#8 from M2BROKER : ConsumerInfo
{commandId = 4, responseRequired = true, consumerId =
ID:ITEM-57186-2408-1236939587882-0:0:1:1, destination = queue://Q1,
prefetchSize = 1000, maximumPendingMessageLimit = 0, browser = false,
dispatchAsync = true, selector = null, subscriptionName = null, noLocal =
false, exclusive = false, retroactive = false, priority = 0, brokerPath =
null, optimizedAcknowledge = false, noRangeAcks = false, additionalPredicate
= null}
Log on M2BROKER
2009-03-13 11:16:20,806 [vm://M2BROKER#0] INFO DemandForwardingBridge
- Network connection between vm://M2BROKER#0 and
tcp://ITEM-57186.dhcp.ancy.fr.sopra/172.16.177.252:61616(M1BROKER) has been
established.
2009-03-13 11:19:48,070 [6.177.252:61616] DEBUG DemandForwardingBridge
- M2BROKER Ignoring Subscription ConsumerInfo {commandId = 4,
responseRequired = false, consumerId =
ID:ITEM-57186-2390-1236939359731-6:1:1:2, destination = queue://Q1,
prefetchSize = 1000, maximumPendingMessageLimit = 0, browser = false,
dispatchAsync = true, selector = null, subscriptionName = null, noLocal =
false, exclusive = false, retroactive = false, priority = 0, brokerPath =
[ID:ITEM-57186-2403-1236939380150-0:0], optimizedAcknowledge = false,
noRangeAcks = false, additionalPredicate =
org.apache.activemq.command.networkbridgefil...@1263db} restricted to 1
network hops only
Do you want other element ?
--
View this message in context:
http://www.nabble.com/How-post-message-to-a-queue-which-is-an-a-remote-broker-tp22493831p22493831.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
