Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (nike.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <25860454.post@talk.nabble.com>
Date: Mon, 12 Oct 2009 11:02:16 -0700 (PDT)
From: Joe Fernandez <joe.fernandez@ttmsolutions.com>
To: users@activemq.apache.org
Subject: Re: Please help me get rendezvous working!!!
In-Reply-To: <25860120.post@talk.nabble.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
References: <25860120.post@talk.nabble.com>


Here are some snippets taken from the=20
http://www.ttmsolutions.com/Apache_Software/ActiveMQ_Reference_Guide.php
ActiveMQ Reference Guide . You'd use a 'ssl' connector instead of 'tcp'.=20
Hope this helps=20

To configure a broker and client to discover each other using the rendezvou=
s
connector, specify the rendezvous connector URI for the discoveryURI
attribute of the broker=E2=80=99s transport connector, as shown in this bro=
ker
configuration file example.

<transportConnectors>
    <transportConnector=20
        name=3D"default"=20
        uri=3D"tcp://localhost:61616"
        discoveryURI=3D"rendezvous://group1"
    />
</transportConnectors>

For the corresponding client configuration, enclose the rendezvous connecto=
r
URI in a discovery URI, and specify the groupname that was used for the
broker=E2=80=99s discoveryURI attribute. This example is from a client=E2=
=80=99s
jndi.properties file.=20

java.naming.factory.initial =3D
org.apache.activemq.jndi.ActiveMQInitialContextFactory

# use the following property to specify the JNDI names for the connection
factories=20
connectionFactoryNames =3D local, rdisc

# These are the URLs or URIs to use for the abovementioned connection
# factories
connection.local.brokerURL =3D tcp://linux02:61616
connection.rdisc.brokerURL =3D discovery:(rendezvous://group1)

Use caution if your consumer is registering a durable subscription and is
also being given a randomized list of brokers to connect with (e.g., via th=
e
discovery URI). After starting and stopping multiple times, the consumer ma=
y
register the same durable subscription with all the brokers on the list. A
broker that receives a message from a publisher for that particular durable
subscription will forward a copy of the message on to other brokers that
also have that durable subscription. In effect, this causes the messages to
be needlessly copied to all the brokers in the network with that durable
subscription.
It is recommended that you always use the maxReconnectAttempts transport
option with the discovery connector. If you do not specify this option and
there are no brokers available on the network, then the Connection.start()
method will hang your client until a broker does become available.

The ActiveMQ distribution includes the jmDNS package in the
$ACTIVEMQ_HOME/lib/optional/jmdns-<version>.jar file. When running a client=
,
the CLASSPATH must include this file.

Joe
http://www.ttmsolutions.com


yesnid wrote:
>=20
> Hello All,
>=20
> I am trying to get my system working, I need to use rendezvous, to
> discover brokers in my system but I want to encrypt the channel with SSL,
> does anyone know how I can configure this to work? HELP PLEASE!!!
>=20

--=20
View this message in context: http://www.nabble.com/Please-help-me-get-rend=
ezvous-working%21%21%21-tp25860120p25860454.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.