I am using AMQ4.1.
I have two JVM processes running (on different physical servers). I would
like each VM to have an embedded broker and yet connect to the peer VM's
embedded broker.
Finally, I would like subscribers on both the VMs to receive published messages
on the topic regardless of whether the message was published on VM1 or on VM2.
It appears based on the description in the docs that peer transport
accomplishes this.
What is not clear to me is this: once the broker comes up on VM1, to which port
should
the second VM connect to on broker 1?
E.g.:
VM1 broker: peer://partyline/group1?persistant=false
VM2 broker: peer://partyline/group1?persistant=false
How can I now have VM1 connect to the second broker and vice versa?
>From the logs of VM1, I see that transport connectors are started at
vm://defaultgroup and tcp://myhost.xxx.com:4454. Does this mean I must
configure VM2 to listen to broker at tcp://myhost.xxx.com:44541 (and vice versa
for VM1)?
INFO: ActiveMQ 4.1.0-incubator JMS Message Broker (group1) is starting
Mar 20, 2007 10:54:37 AM org.apache.activemq.broker.BrokerService getBroker
INFO: For help or more information please see:
http://incubator.apache.org/activemq/
Mar 20, 2007 10:54:37 AM
org.apache.activemq.transport.TransportServerThreadSupport doStart
INFO: Listening for connections at: tcp://myhost.xxx.com:44541
Mar 20, 2007 10:54:37 AM org.apache.activemq.broker.TransportConnector start
INFO: Connector tcp://myhost.xxx.com:44541 Started
Mar 20, 2007 10:54:37 AM org.apache.activemq.network.NetworkConnector doStart
INFO: Network Connector bridge Started
Mar 20, 2007 10:54:37 AM org.apache.activemq.broker.BrokerService start
INFO: ActiveMQ JMS Message Broker (defaultgroup,
ID:myjost.xxx.com-54303-1174413277517-1:0) started
Mar 20, 2007 10:54:37 AM org.apache.activemq.broker.TransportConnector start
INFO: Connector vm://defaultgroup Started
Regards
/U
