directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kiran Ayyagari (JIRA)" <>
Subject [jira] Closed: (DIRSERVER-443) JNDI Event delivery should be asynchronous in a separate thread
Date Mon, 18 Oct 2010 20:54:26 GMT


Kiran Ayyagari closed DIRSERVER-443.

    Resolution: Invalid

This is no longer valid cause we don't rely on JNDI in the code anymore

> JNDI Event delivery should be asynchronous in a separate thread
> ---------------------------------------------------------------
>                 Key: DIRSERVER-443
>                 URL:
>             Project: Directory ApacheDS
>          Issue Type: New Feature
>          Components: core
>            Reporter: Alex Karasulu
>            Assignee: Alex Karasulu
>             Fix For: 2.0.0-RC1
> Presently the JNDI event notification mechanism in the JNDI provider delivers JNDI Events
to listeners in the same thread as the LDAP operation processing thread.  This is not good
because it can interfer with and/or delay the response to the original LDAP operation. 
> We need to make the EventService asynchronously deliver these events in a separate thread
so the LDAP operation is not effected by bad listener implementations.  The response then
is uneffected.  The LDAP operation thread should just enqueue events on an event queue which
are delivered to listeners in a sparate event processing thread.

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

View raw message