IBM FileNet P8, Version 5.2.1            

Intermittent "socket closed" exception with Active Directory

Content Platform Engine might throw a "socket closed" exception when the LDAP provider is Microsoft Active Directory.

Symptoms

Content Platform Engine might intermittently throw the following exception when performing an LDAP search operation against Microsoft Active Directory:

LDAP search operation failed: hqpsidc:3268; socket closed

When the exception occurs, Content Platform Engine will try the operation again and will successfully establish the connection.

Causes

For Content Platform Engine version 5.2, improvements were made to the LDAP provider cache. As a result, the LDAP connections remain active (and idle) longer. In some cases, Microsoft Active Directory determines a connection has remained idle for too long and closes it on the Active Directory side. As a result, when user actions trigger LDAP searches, the Content Platform Engine tries to use the closed connection and throws an exception.

Resolving the problem

Set the JVM argument com.sun.jndi.ldap.connect.pool.timeout to a small timeout value, forcing Content Platform Engine to close the connection before the Active Directory server closes the connection. For example, the following timeout setting is for 30 minutes, in milliseconds:

 -Dcom.sun.jndi.ldap.connect.pool.timeout=1800000

You can also add the JVM argument as an entry to the FileNet.properties file.



Last updated: March 2016
p8pct009.htm

© Copyright IBM Corporation 2016.