Bug ID: JDK-5053613 JNDI connection pooling creating multiple pools for the same credentials

Type: Bug
Component: core-libs
Sub-Component: javax.naming
Affected Version: 8.0pe

Priority: P3
Status: Closed
Resolution: Not an Issue
OS: solaris_8
CPU: sparc

Submitted: 2004-05-27
Updated: 2016-06-06
Resolved: 2005-09-19

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) 
======================================================================

EVALUATION I have not been able to gather further information from the customer who reported this bug. Without this information it does not seem that we can resolve it. If you would like us to further investigate this bug please send us a new report, include this bug number, also include details of the pool log or an example to reproduce the problem. Submit the report to : http://bugs.sun.com/services/bugreport/index.jsp

19-09-2005

EVALUATION This bug looks more like a J2SE JNDI issue. Need to assign it to the J2SE JNDI team. ###@###.### 8/30/04 18:41 GMT -------------------------------------- Looking at the pool log, a new pool is being created for a connection belonging to a pool that doesn't already exist (may have expired). Either the identity of the existing pool: @f145a and the new connection's id don't match or the existing pool with the same id has expired and no longer available. There is no information in the bug description to explain which of these two is taking place. But either way it's not a bug. We can wait for further information from the customer with either more details of the pool log or an example to reproduce the problem. I am assuming that the webbug team will contact the customer to get more information. ###@###.### 9/15/04 05:47 GMT The information requested above has not been provided to date. We still can't tell if there is a real bug here, or if there is, how to reproduce it. Setting status to incomplete. ###@###.### 2005-04-08 20:36:16 GMT

30-08-2004