activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From janylj <>
Subject Re: ActiveMQ JNDI support only for testing?
Date Tue, 17 Mar 2009 17:45:58 GMT

Thanks James for a great suggestion of Apache Directory Server. I didn't know
that Apache Directory Server could be deployed in the same JVM as ActiveMQ

Do you happen to know whether Apache Directory Server have similar failover
url as ActiveMQ? For example, we have a pair of HA broker (A and AFailover).
If A goes down, the JMS client would automatically re-connect to AFailover
through failover url. Because Apache Directory Server is deployed in the
same JVM of A, A goes down, the JNDI of A also goes down. Can JNDI be
automatically failed over to AFailover?

Thanks again.

James.Strachan wrote:
> 2009/3/17 janylj <>:
>> I was trying to have a centralized repository of destinations and
>> ConnectionFactory. I could use a uniform namespace for destination to
>> avoid
>> conflicting. However, I don't want to allow users creating destination or
>> ConnectionFactory on the fly. I would like them accessing the broker only
>> through administrative objects.
>> Because my clients are not running inside J2EE container, I am using LDAP
>> for JNDI. I wish ActiveMQ has a built JNDI server in the broker side.
>> Therefore, I don't have to deploy another LDAP server and worry about its
>> HA
>> solution and other topics that we have already invested in the broker
>> side.
> A message broker is kinda different from a HA LDAP server - however
> you can just deploy Apache Directory Server in the same JVM as the
> broker if you like...
> -- 
> James
> -------
> Open Source Integration

View this message in context:
Sent from the ActiveMQ - User mailing list archive at

View raw message