Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-5053613

JNDI connection pooling creating multiple pools for the same credentials

    Details

    • Type: Bug
    • Status: Closed
    • Priority: P3
    • Resolution: Not an Issue
    • Affects Version/s: 8.0pe
    • Fix Version/s: None
    • Component/s: core-libs

      Description

      Name: rl43681 Date: 05/26/2004


      FULL PRODUCT VERSION :
      java version "1.4.1_05"
      Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1_05-b01)
      Java HotSpot(TM) Client VM (build 1.4.1_05-b01, mixed mode)


      FULL OS VERSION :
      SunOS wsqeai01 5.8 Generic_108528-19 sun4u sparc SUNW,Sun-Fire-480R

      A DESCRIPTION OF THE PROBLEM :
      The jndi connection pooling seems to be creating multiple connection pools for the same credentials. Here is the logs that shows it:

      com.sun.jndi.ldap.pool.Pool@19ba640{}.get(): creating new connections list for 1
      XX.XX.XX.XXX:389:::cn=xxx,ou=Users,ou=Administration,o=xxxx
      ###@###.### size=1; size: 0
      ###@###.### size=4; size: 0
      ###@###.###erred size=0; size: 0
      ###@###.###ase(): com.sun.jndi.ldap.LdapClien
      t@3bd64e; size: 4
      ###@###.###ase(): release com.sun.jndi.ldap.L
      dapClient@3bd64e; size: 4

      It created a new pool @117416e while there is already a pool @f145a having a size of 4.


      STEPS TO FOLLOW TO REPRODUCE THE PROBLEM :
      There is no specific steps to recreate it but do noticed it to start happening after the first pool expires.


      SERVER LOG FILE :
      com.sun.jndi.ldap.pool.Pool@19ba640{}.get(): creating new connections list for 1
      XX.XX.XX.XXX:389:::cn=xxx,ou=Users,ou=Administration,o=xxxx
      ###@###.### size=1; size: 0
      ###@###.### size=4; size: 0
      ###@###.###erred size=0; size: 0
      ###@###.###ase(): com.sun.jndi.ldap.LdapClien
      t@3bd64e; size: 4
      ###@###.###ase(): release com.sun.jndi.ldap.L
      dapClient@3bd64e; size: 4


      REPRODUCIBILITY :
      This bug can be reproduced occasionally.

      CUSTOMER SUBMITTED WORKAROUND :
      There is no workaround. Just a nuisance because it exceeds the max connection and would start getting communication errors.
      (Incident Review ID: 275054)
      ======================================================================

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jhangalsunw Jayalaxmi Hangal (Inactive)
                Reporter:
                rlewis Roger Lewis (Inactive)
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Imported:
                  Indexed: