When encountering timeout errors in data store connections, you might want to increase the timeout values. Usually the default timeout values are fine. However in case your installation contains large amounts of certain kind of data, some requests may take longer than what the defaults allow.

CustomerID WildFly transaction timeout configuration for connections to PostgreSQL database

You can configure the transaction timeout using jboss-cli:

• In standalone mode:
  • /subsystem=transactions:write-attribute(name=default-timeout,value=500)
• In domain mode:
  • /profile=full/subsystem=transactions:write-attribute(name=default-timeout,value=500)

LDAP connection read timeout configuration for connections to any LDAP (OpenLDAP, AD LDS, Active Directory)

You can configure the connection read timeout either in the jndi.properties file or in the Service configuration (Configuration String section) in SSO Management:

• com.sun.jndi.ldap.read.timeout = 500000

Related configuration options are:

• com.sun.jndi.ldap.connect.timeout
  • Timeout for socket connections (default is 15000, or 15 seconds)
• com.ubisecure.util.ldap.maxage
  • Max age for connections, a connection is re-opened after this time (default is 120000, or 2 minutes)

Related articles

• Page:
  Adaminstall.cmd fails with INSUFF_ACCESS_RIGHTS error.
• Page:
  Use Directory User Mapping with SQL databases
• Page:
  Configure timeout values for data store connections
• Page:
  CustomerID SQL query troubleshooting