Hello Joe, Thank you for the quick reply, I tried what you are suggesting before however, it didn't work for me. My setup will work perfectly via ssl and no discovery, and if I try discovery with tcp it works fine however when I try to combine the two my clients just spin trying to connect to the broker and never being able to do so. Any Help you can give would be greatly appreciated, I am really stuck and I really really need to get this working!!
Thank you. Joe Fernandez wrote: > > Here are some snippets taken from the > http://www.ttmsolutions.com/Apache_Software/ActiveMQ_Reference_Guide.php > ActiveMQ Reference Guide . You'd use a 'ssl' connector instead of 'tcp'. > Hope this helps > > To configure a broker and client to discover each other using the > rendezvous connector, specify the rendezvous connector URI for the > discoveryURI attribute of the broker’s transport connector, as shown in > this broker configuration file example. > > <transportConnectors> > <transportConnector > name="default" > uri="tcp://localhost:61616" > discoveryURI="rendezvous://group1" > /> > </transportConnectors> > > For the corresponding client configuration, enclose the rendezvous > connector URI in a discovery URI, and specify the groupname that was used > for the broker’s discoveryURI attribute. This example is from a client’s > jndi.properties file. > > java.naming.factory.initial = > org.apache.activemq.jndi.ActiveMQInitialContextFactory > > # use the following property to specify the JNDI names for the connection > factories > connectionFactoryNames = local, rdisc > > # These are the URLs or URIs to use for the abovementioned connection > # factories > connection.local.brokerURL = tcp://linux02:61616 > connection.rdisc.brokerURL = 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 > the discovery URI). After starting and stopping multiple times, the > consumer may 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: >> >> Hello All, >> >> 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!!! >> > > -- View this message in context: http://www.nabble.com/Please-help-me-get-rendezvous-working%21%21%21-tp25860120p25860521.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
