[#DIRSERVER-443] JNDI Event delivery should be asynchronous in a separate thread

Directory ApacheDS

JNDI Event delivery should be asynchronous in a separate thread

Created: 26/Oct/05 01:21 AM Updated: 09/Jul/08 11:46 AM

Return to search

Component/s:

core

Affects Version/s:

None

Fix Version/s:

2.0.0

Time Tracking:

Not Specified

Description

« Hide

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.

All

Comments

Work Log

Change History

Subversion Commits

Sort Order:

Alex Karasulu made changes - 10/Feb/06 12:42 PM

Field	Original Value	New Value
Project	Directory Server [ 10516 ]	Directory ApacheDS [ 12310260 ]
Key	DIREVE-287	DIRSERVER-443

Alex Karasulu made changes - 10/Feb/06 02:14 PM

Component/s

core [ 12310713 ]

[ Permlink | « Hide ]

Emmanuel Lecharny added a comment - 09/Jul/08 11:46 AM

Let's be optimistic, and affect this issue to 2.0

Emmanuel Lecharny made changes - 09/Jul/08 11:46 AM

Fix Version/s

2.0.0 [ 12312396 ]