Using JAVASSO Participant Application, OC4J Keeps Too Many Connections Against the 3rd Ldap Server
(Doc ID 779516.1)
Last updated on APRIL 27, 2020
Applies to:Oracle Containers for J2EE - Version 10.1.3.1.0 to 10.1.3.4.0 [Release AS10gR3]
Information in this document applies to any platform.
This problem can occur on any platform.
When accessing a Java SSO participant application that has been configured to use LDAP server Security Provider, each one of the single accesses to a protected resource, ends in an LDAP server access, even if the JSSO existing session is correctly identified.
a) The first time a user access to the application, the LDAP access to validate user name with the provider credentials and retrieves a valid subject,
The consequences of this are that the performance of the application is not as good as expected, and also the LDAP server gets a continuous increase of new connections that at the end forces to restart it.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document