[
https://issues.apache.org/jira/browse/JS2-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ate Douma resolved JS2-575.
---------------------------
Resolution: Fixed
Fix Version/s: 2.1-dev
2.1
I've resolved this issue in a different and less intrusive way, using a Proxy
for the LdapContext.
See: http://svn.apache.org/viewvc?view=rev&rev=504946
> 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: https://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
> Assigned To: Ate Douma
> Fix For: 2.1, 2.1-dev
>
> Attachments: jetspeed-security-2.1-dev_20061109.jar, ldapImpl.zip,
> ldapImpl_r2.zip
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
