activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mathieu Guillaume <...@voxmobili.com>
Subject Re: Network of brokers + multicast discovery, programmatically
Date Mon, 17 Dec 2007 14:24:38 GMT
That looks much more simple!

I do have one problem remaining with that setup though : my messages
seem to be discarded by the listener because of a TTL=1, and I didn't
find anyplace to change it.
My test config is a sender on a host and a listener on another host. The
message I get on the listener is this:

[ActiveMQ Transport: tcp://mysystem/192.168.0.1:61616] DEBUG
org.apache.activemq.network.DemandForwardingBridge  - localhost Ignoring
Subscription ConsumerInfo {commandId = 4, responseRequired = false,
consumerId = ID:mysystem-60155-1197900986277-5:1:1:1, destination =
topic://my.test, prefetchSize = 1000, maximumPendingMessageLimit = 0,
browser = false, dispatchAsync = true, selector = null, subscriptionName
= null, noLocal = false, exclusive = false, retroactive = false,
priority = 0, brokerPath = [ID:myothersystem-35326-1197901007699-0:0],
optimizedAcknowledge = false, noRangeAcks = false, additionalPredicate =
org.apache.activemq.command.NetworkBridgeFilter@156b6b9} restricted to 1
network hops only


Hiram Chirino wrote:
> You never need to add the vm transport:
> 
> broker.addConnector("vm://localhost:61616");
> 
> it gets created/destroyed on the fly. Also make sure the all the
> brokers have unique broker names.  And all the steps you are doing are
> done automatically using the peer transport [1].  Like:
> 
> new ActiveMQConnectionFactory("peer://group-a/broker-a");
> 
> Starts up an embedded broker named broker-a and configures it to join
> the group-a multicast broker group.
> 
> 
> [1] http://activemq.apache.org/peer-transport-reference.html


Mime
View raw message