|
If you were logged in you would be able to see more operations.
|
|
|
|
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.
|
|
Description
|
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. |
Show » |
| There are no subversion log entries for this issue yet.
|
|
New Feature
Open
Major
JNDI Event delivery should be asynchronous in a separate thread
