directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sathyanarayan, Harish" <>
Subject RE: problem with starting JDBM partition
Date Wed, 30 Aug 2017 12:27:06 GMT
Is it just me who is getting this issue with JDBM partition, I am hesitant to use apachedDS
instance in production with this partition issue. If anyone solved this issue,  let me know?

-----Original Message-----
From: Sathyanarayan, Harish 
Sent: Tuesday, August 29, 2017 12:27 PM
To: 'Apache Directory Developers List' <>
Subject: RE: problem with starting JDBM partition

Hi Emmanuel

I guess you hv described the sequence fairly accurate.  Anyway here is how it goes: 1. Start
embedded instance  with partition and contextentry injection 2. Check the partition location
- files created, check apacheds studio, - partition and contextentry created as intended 3.
Stop and restart 4. Contextentry disappears 5. Stop and restart 6. Contextentry shows up.

Beats me!

-----Original Message-----
From: Emmanuel Lécharny [] 
Sent: Tuesday, August 29, 2017 9:04 AM
Subject: Re: problem with starting JDBM partition

Le 29/08/2017 à 14:52, Sathyanarayan, Harish a écrit :
> Hey Guys
> Not sure if any of you ran into this but kind of a weird problem with M23 verison of
ApacheDS. The context entry created for a JDBM partition does not show up only at the second
time of restarting the embedded server instance. It works fine from the 3rd time onwards.
I am reasonably sure that the partition is created correctly and initialized.  Has anyone
seen this problem.?


can you describe the exact sequence you are using ?

Like :
- Configuring a partition
- starting ApacheDS and injecting a contextEntry (it shows up when looking for it)
- Stopping ApacheDS
- Starting ApacheDS : the contextEntry does not show up
- Stopping ApacheDS and statrting it again : the contextEntry shows up.

Thanks !

Emmanuel Lecharny

The information contained in this electronic mail transmission may be privileged and confidential,
and therefore, protected from disclosure. If you have received this communication in error,
please notify us immediately by replying to this message and deleting the email and its attachments
from all computers without copying or disclosing it.
View raw message