[
https://issues.apache.org/jira/browse/DIRSERVER-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Emmanuel Lecharny updated DIRSERVER-443:
----------------------------------------
Fix Version/s: 2.0.0
Let's be optimistic, and affect this issue to 2.0
> JNDI Event delivery should be asynchronous in a separate thread
> ---------------------------------------------------------------
>
> Key: DIRSERVER-443
> URL: https://issues.apache.org/jira/browse/DIRSERVER-443
> Project: Directory ApacheDS
> Issue Type: New Feature
> Components: core
> Reporter: Alex Karasulu
> Assignee: Alex Karasulu
> Fix For: 2.0.0
>
>
> 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.
