Hi Joe It's what I suspected. It's not suit me unfortunately.
I would like to have several multicast groups (and one network connector by group) but not on a single LAN. I would like that a local broker can request a "WAN distant directory server (with known fixed IP)" to make a multicast choice (associated to a group) for him, and send it the answer. And I would like that this discovery process can be repeated automatically when the network connection with the distant broker is down. Do you advise me not to try to write my own Directory Agent ? Eric-AWL Joe Fernandez wrote: > > I haven't looked closely at the LdapNetworkConnector source, but I suspect > it will connect to all the brokers that result from the corresponding LDAP > search operation. > > Joe > http://www.ttmsolutions.com > > > Eric-AWL wrote: >> >> <networkConnectors> >> <ldapNetworkConnector uri="ldap://myldap.mydomain.com:389"; >> base="dc=brokers,dc=mydomain,dc=com" >> anonymousAuthentication="true" >> searchFilter="(cn=*)" >> searchScope="SUBTREE_SCOPE" >> /> >> </networkConnectors> >> >> Ok for uri="failover:(ldap:://ldapserver1,ldap://ldapserver2)" which >> concerns the failover of ldapserver. >> >> But my question concerned the ldap directory itself, if under "base" >> (dc=brokers,dc=mydomain, dc=com), I put more than one LDAP entries which >> can all be considered as a network broker. Which server will be chosen >> and how ? >> >> Eric-AWL >> >> >> >> >> James.Strachan wrote: >>> >>> 2008/8/21 Eric-AWL <[EMAIL PROTECTED]>: >>>> >>>> Hi every body >>>> >>>> I'm not an LDAP expert so I expect I don't make too many mistakes in my >>>> explications. >>>> >>>> If we put several server references under the same RDN, does the >>>> discovery >>>> mechanism choose one of them with a round-robin algorithm ? >>>> >>>> What happens if the server associated with this reference doesn't work >>>> ? >>>> Does the discovery mechanism choose an other ? >>>> >>>> What happens exactly when we add or remove one reference in the LDAP >>>> directory structure ? >>> >>> ActiveMQ typically uses the Failover protocol with all discovery >>> mechanisms - so that if a discovered (or static) broker entry is no >>> longer valid the client will auto-reconnect to another broker - you >>> can configure the algorithm to use round robin or random along with >>> various other things... >>> >>> http://activemq.apache.org/failover-transport-reference.html >>> >>> >>> -- >>> James >>> ------- >>> http://macstrac.blogspot.com/ >>> >>> Open Source Integration >>> http://open.iona.com >>> >>> >> >> > > -- View this message in context: http://www.nabble.com/LDAP-Discovery-mechanism---round-robin-choice-tp19090881p19092039.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
