Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-4635

LDAP connection pool settings are not being respected

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Low Low
    • None
    • 2.8, 2.8.4
    • None
    • None

      Steps to reproduce

      1. In Crowd 2.8.4, navigate to Cogwheel Menu > LDAP connection pool
      2. Modify the values in each of the the connection pool settings
      3. Restart Crowd
      4. Go back to the same page

      Expected results

      The "LDAP connection pool statistics" report at the top will reflect the connection pool settings previous inputted

      Actual results

      The "LDAP connection pool statistics" report shows the same starting values each time:

      ***** start *****
      idle timeout: 0
      maximum pool size: 0
      preferred pool size: 0
      initial pool size: 1
      protocol types: plain ssl
      authentication types: none simple 
      ...
      

      Other notes

      In earlier versions of Crowd, such as 2.8.0, the "LDAP connection pool statistics" report is not available from the UI. However, one can still validate that Crowd is still affected by this issue by setting the following JVM startup parameter:

      -Dcom.sun.jndi.ldap.connect.pool.debug=all
      

      The same LDAP connection report can be seen at the very beginning of Crowd startup in Tomcat logs, at <crowd_install>/apache-tomcat/logs/catalina.out

      Workaround

      Setting the parameters directly via JVM parameters still works:

      com.sun.jndi.ldap.connect.pool.authentication
      com.sun.jndi.ldap.connect.pool.debug
      com.sun.jndi.ldap.connect.pool.initsize
      com.sun.jndi.ldap.connect.pool.maxsize
      com.sun.jndi.ldap.connect.pool.prefsize
      com.sun.jndi.ldap.connect.pool.protocol
      com.sun.jndi.ldap.connect.pool.timeout
      

      Reference: http://docs.oracle.com/javase/jndi/tutorial/ldap/connect/config.html

            Unassigned Unassigned
            rchang Robert Chang
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: