Mailing-List: contact dev-help@directory.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache Directory Developers List" <dev@directory.apache.org>
Message-ID: <415512306.1234704900351.JavaMail.jira@brutus>
Date: Sun, 15 Feb 2009 05:35:00 -0800 (PST)
From: "Emmanuel Lecharny (JIRA)" <jira@apache.org>
To: dev@directory.apache.org
Subject: [jira] Closed: (DIRSERVER-290) Allow the installation of the
 shutdown handler to be optional for embedded servers
In-Reply-To: <1759139090.1138199469476.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DIRSERVER-290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Lecharny closed DIRSERVER-290.
---------------------------------------


closed

> Allow the installation of the shutdown handler to be optional for embedded servers
> ----------------------------------------------------------------------------------
>
>                 Key: DIRSERVER-290
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-290
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>    Affects Versions: pre-1.0
>         Environment: Windows/UNIX JDK 1.4 - Embedded server within JBoss
>            Reporter: Simon Temple
>            Assignee: Alex Karasulu
>            Priority: Minor
>             Fix For: 1.0-RC1
>
>
> I am using the directory embedded in JBoss.  When we shutdown JBoss our
> application services need to remove certain entries from the directory.
> Unfortunately the shutdown handler in DefaultDirectoryServices closes Eve
> out before we get chance to finish and we get errors:
> org.apache.ldap.common.exception.LdapServiceUnavailableException:
> Context operation unavailable when invoked after Eve provider has been
> shutdown
> When our services finally stop, we stop the directory using the
> ShutdownConfiguration class so we don't really need the additional shutdown
> thread.
> I've commented out the shutdown hook code and our server is now behaving
> how we want but I don't like running with patched source...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.