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

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0-FINAL, 2.1-dev
• Fix Version/s: 2.1-dev, 2.1
• Component/s: Security
• Environment: Apache Tomcat 5.5.17
• Assignee: Ate Douma
• Reporter: Eivinn Hustveit
• Created: 09/Aug/06 09:08
• Updated: 04/Oct/11 21:37
• Resolved: 08/Feb/07 16:40

Description

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.