directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Karasulu (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DIRSERVER-443) JNDI Event delivery should be asynchronous in a separate thread
Date Fri, 10 Feb 2006 05:15:17 GMT
     [ http://issues.apache.org/jira/browse/DIRSERVER-443?page=all ]

Alex Karasulu updated DIRSERVER-443:
------------------------------------

    Component: core

> JNDI Event delivery should be asynchronous in a separate thread
> ---------------------------------------------------------------
>
>          Key: DIRSERVER-443
>          URL: http://issues.apache.org/jira/browse/DIRSERVER-443
>      Project: Directory ApacheDS
>         Type: New Feature
>   Components: core
>     Reporter: Alex Karasulu
>     Assignee: Alex Karasulu

>
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message