Caused by: javax.naming.NamingException: LDAP response read timed out, timeout used: 600000 ms.

Hello, I think we have the same issue as described in the following posts:


https://community.opentext.com/cyberres/iga/idm/f/discussions/519695/has-anyone-noticed-and-hopefully-fixed-the-problem-with-ldap-timeouts-that-started-to-show-up-after-upgrading-to-4-8-6?tkKey=weRRAxz9sZqdaiiXN7KuI

 The first workflow submit of the day fails. UserApp 4.8.5 

 Identity Apps - intermittent access issue / 403 

The first one is the one that is the same as ours, others seems to be related.

The error changes to the value set in the ism-configuration.properties "com.novell.ldap.timeout" value. Timeout applies to idle time, so error happens after nobody logs in for 10 minutes (whenever somebody logs in the time is extended for 10 minutes).

So the general problem is that after that time when user logs in empty page is displayed with 504 gateway timeout issue and in catalina.out (Caused by: javax.naming.NamingException: LDAP response read timed out, timeout used: 600000 ms.) errors is reported. We are dealing with the 504 issue separately but we would like to also clear the Catalina error.

Another thing we noticed this LDAP issue only started happening after we switched to LDAP LB Layer 4.

HA proxy is used for it with configuration:

timeout server          10m
timeout connect         1s

Because of it we set ism-configuration.properties "com.novell.ldap.timeout" value to 300000 (but the same issue happens).

Any comments, or best solutions are welcome.

Currently researching this one: community.opentext.com/.../idm-apps-ldap-connections