On 7/30/06, jcarreira <
jcarreira@...> wrote:
>
>
> James.Strachan wrote:
> >
> > Am not too sure what your XML looks like - but the peer: transport is
> > typically only used on the client side - there is no server side
> > transport for peer
> >
>
> Well, as per my original post
> (
http://www.nabble.com/Getting-started-with-ActiveMQ-tf2004874.html) I'm
> trying to set it up so that I have independent cluster nodes which can be
> transparently dropped into the cluster and automatically discover each
> other. From the docs and what Hiram said, peer seemed like a good fit. If
> it's creating embedded brokers in each app, why is it client-side, not
> server side?
>
> In any case, I'm setting it up using multicast discovery and a tcp port like
> it shows in the network of brokers example now.
Some transports are purely client side (like multicast and peer) -
some transports have a server side to them (like tcp and http).
Just don't use the peer:// transport connector in the activemq.xml
--
James
-------
http://radio.weblogs.com/0112098/
