portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eivinn Hustveit (JIRA)" <jetspeed-...@portals.apache.org>
Subject [jira] Created: (JS2-575) Sun LDAP connection pooling implementation needed so that Jetspeed does not need to be restarted if LDAP server is restarted or connection is lost.
Date Wed, 09 Aug 2006 09:09:13 GMT
Sun LDAP connection pooling implementation needed so that Jetspeed does not need to be restarted
if LDAP server is restarted or connection is lost.
---------------------------------------------------------------------------------------------------------------------------------------------------

                 Key: JS2-575
                 URL: http://issues.apache.org/jira/browse/JS2-575
             Project: Jetspeed 2
          Issue Type: Improvement
          Components: Security
    Affects Versions: 2.1-dev, 2.0-FINAL
         Environment: Apache Tomcat 5.5.17
            Reporter: Eivinn Hustveit


The Jetspeed-2 LDAP security implementation holds on the ldap context during the whole server
lifecycle. This means that if the connection to the ldap server, in my case OpenLDAP, is lost
we have to restart the Apache Tomcat server which is unneccesary.

The proposed fix is to use standard SUN jndi implementation for LDAP connection pooling. After
the connection pool has been setup it will be automatically managed by the VM.

-- 
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

        

---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


Mime
View raw message