[GLASSFISH-21527] CLONE - External LDAP connection randomly closing Created: 10/Mar/16  Updated: 10/Mar/16

Status: Open
Project: glassfish
Component/s: security
Affects Version/s: None
Fix Version/s: 3.1

Type: Bug Priority: Minor
Reporter: javacentrum Assignee: kumarjayanti
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Solaris
Platform: Sun


Issue Links:
Cloners
clones GLASSFISH-5146 External LDAP connection randomly clo... Resolved
Issuezilla Id: 5,146

 Description   

An external LDAP connection is configured as an external JNDI resource. The
LDAP connection and deployed applications work fine.

If the system is then left idle for an hour or so the LDAP connection gets
closed. I am not sure who is closing the connection but glassfish is not aware
that the connection has been closed. The next time the application is used, it
throws an exception when it tries to use the closed connection.

If an external LDAP server times out the connection, Glassfish should know this
and try to reestablish the connection the next time it is needed.

I get the following exception when I try to use the connection. The only way to
get it back is to restart the app server.

javax.naming.CommunicationException: connection closed [Root exception is
java.io.IOException: connection closed];

Caused by: java.io.IOException: connection closed
at com.sun.jndi.ldap.LdapClient.ensureOpen(LdapClient.java:1558)
at com.sun.jndi.ldap.LdapClient.search(LdapClient.java:504)
at com.sun.jndi.ldap.LdapCtx.doSearch(LdapCtx.java:1944)



 Comments   
Comment by javacentrum [ 10/Mar/16 ]

I have same problem in GF 3.1.2.2 on Sun Solaris 10 and Linux 64bit (kernel 4.2.0-30-generic). No matter if I closing context or not after use. I don't understand why is bug 5146 marked as Resolved/Fixed.





Generated at Mon Feb 27 00:47:12 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.