On 9/25/06, gabriel kastenbaum <[EMAIL PROTECTED]> wrote:
Hi everybody,
Can we use several <transportConnector> in the same configuration.
And can they share the same destinations - using clustering ?
Yes.
Note that an individual transportConnector is just a different
port/transport/protocol, you are still talking to the same broker &
destinations.
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>
I'd recommend using multicast for discovery and then using tcp for the
actual transports - its very reliable and fast.
--
James
-------
http://radio.weblogs.com/0112098/
