Mailing-List: contact users-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@directory.apache.org
Received-SPF: pass (nike.apache.org: domain of jdisher@parad.net designates
 72.13.95.234 as permitted sender)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1251.1)
Subject: Re: ApacheDS on production
From: Jonathan Disher <jdisher@parad.net>
In-Reply-To: <1319216491.19977.YahooMailClassic@web130201.mail.mud.yahoo.com>
Date: Fri, 21 Oct 2011 14:22:57 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <E7FD99C7-0ED8-4680-83CA-4CBB5249332B@parad.net>
References: <1319216491.19977.YahooMailClassic@web130201.mail.mud.yahoo.com>
To: users@directory.apache.org

You also don't have working replication.

If you want more than one server,  you have to apply updates to each =
server separately.

This for me is a deal breaker, but YMMV.

-j

On Oct 21, 2011, at 10:01 AM, Harakiri wrote:

>=20
>=20
> --- On Thu, 10/20/11, Alex Pershyn <Alex.Pershyn@enabil.com> wrote:
>=20
>> From: Alex Pershyn <Alex.Pershyn@enabil.com>
>> Subject: ApacheDS on production
>> To: "users@directory.apache.org" <users@directory.apache.org>
>> Date: Thursday, October 20, 2011, 10:49 AM
>> Hi all,
>> Does anybody have an experience of using ApacheDS on
>> production? Was it stable? Did you have any issues and how
>> you resolved them?
>=20
> I have experience with this, the 1.5.x is generally stable (for what i =
do - custom partition, just some lookups - nothing fancy) - however =
there is one major issue that requires a cronjob to restart the service =
every night
>=20
> https://issues.apache.org/jira/browse/DIRSERVER-1620
>=20
> If you can live with that, i say give it a shot.
>=20
> I do hope the issue gets resolved for 2.0 tho.
>=20
>=20
>>=20