Jetspeed 2
  1. Jetspeed 2
  2. 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.

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 2.0-FINAL, 2.1-dev
    • Fix Version/s: 2.1-dev, 2.1
    • Component/s: Security
    • Labels:
      None
    • Environment:
      Apache Tomcat 5.5.17

      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.

      1. ldapImpl.zip
        12 kB
        Eivinn Hustveit
      2. ldapImpl_r2.zip
        13 kB
        Eivinn Hustveit
      3. jetspeed-security-2.1-dev_20061109.jar
        155 kB
        Eivinn Hustveit

        Activity

        No work has yet been logged on this issue.

          People

          • Assignee:
            Ate Douma
            Reporter:
            Eivinn Hustveit
          • Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development