You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Alex Karasulu (JIRA)" <di...@incubator.apache.org> on 2005/10/25 18:21:55 UTC
[jira] Created: (DIREVE-287) JNDI Event delivery should be asynchronous in a separate thread
JNDI Event delivery should be asynchronous in a separate thread
---------------------------------------------------------------
Key: DIREVE-287
URL: http://issues.apache.org/jira/browse/DIREVE-287
Project: Directory Server
Type: New Feature
Reporter: Alex Karasulu
Assigned to: 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
[jira] Updated: (DIRSERVER-443) JNDI Event delivery should be
asynchronous in a separate thread
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ 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
[jira] Updated: (DIRSERVER-443) JNDI Event delivery should be
asynchronous in a separate thread
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Closed: (DIRSERVER-443) JNDI Event delivery should be
asynchronous in a separate thread
Posted by "Kiran Ayyagari (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
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: 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-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.
[jira] Updated: (DIRSERVER-443) JNDI Event delivery should be
asynchronous in a separate thread
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ 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-RC1
(was: 2.0.0)
Moved back to 2.0.0-RC1
> 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-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.