Hi everybody,
Can we use several <transportConnector> in the same configuration.
And can they share the same destinations - using clustering ?
Here is the reason of my question:
I have client waiting for topics at a multicast adress.
But the producer of message is on the same machine as one of the consumer.
It means that as long as the consumer is using the Multicast Adress to
listen, the producer can not connect.
"javax.jms.JMSException: Could not connect to broker URL:
multicast://225.0.0.1:61617. Address already in use"
So I thought using a clustered destination to have the same Topic with
two adresses.
One - used by the producer - is in TCP
One - used by the consumer- is in Multicast.
Which leads to something like this:
Am I just doing something too complex for
<transportConnectors>
<transportConnector name="internal" uri="tcp://localhost:61617"
discoveryUri="multicast://225.0.0.1:61618"/>
<transportConnector name="multicast"
uri="multicast://225.0.0.1:61617"
discoveryUri="multicast://225.0.0.1:61618"/>
</transportConnectors>
<networkConnectors>
<networkConnector name="connexion"
uri="multicast://225.0.0.1:61618"/>
</networkConnectors>
2nd question:
Can we do something like this:
Two parallel networks.
One linking the internal and the multicast transportConnectors.
And one linking the localhost adress with others activeMQ via multicast
(for discovery) and TCP (for transport between the nodes)
<transportConnectors>
<transportConnector name="internal" uri="tcp://localhost:61617"
discoveryUri="multicast://225.0.0.1:61618"/>
<transportConnector name="multicast"
uri="multicast://225.0.0.1:61617"
discoveryUri="multicast://225.0.0.1:61618"/>
<transportConnector name="clustering" uri="tcp://localhost:61616"
discoveryUri="multicast://225.0.0.1:61616"/>
</transportConnectors>
<networkConnectors>
<networkConnector name="connexion"
uri="multicast://225.0.0.1:61618"/>
<networkConnector name="clustering"
uri="multicast://225.0.0.1:61616"/>
</networkConnectors>
Promise, if this works, I publish the entire config!
