The Inactivity Timeout of LDAP Load Balancer Causes JAZN-LDAP Applications to Generate HTTP 500 Errors
(Doc ID 781229.1)
Last updated on FEBRUARY 13, 2024
Applies to:
Oracle Containers for J2EE - Version 10.1.3.0.0 to 10.1.3.5.0 [Release AS10gR3]Information in this document applies to any platform.
Symptoms
Oracle Application Server 10.1.3 running a JAZN LDAP protected web application, responds very frequently with HTTP 500 errors when accessing it, and makes it unusable.
In this case, it was a WebServices web application, but the problem is not exclusive to this technology scope.
The configuration of the application is as follows:
- Identity Management 10.1.4.0.1 on High Availability configuration (using LDAP LBR in front of OID)
- The HTTP server of ID Management 10.1.4.0.1 is used as HTTP front end to delegate work to 10.1.3.1.0 OC4J instances running internally.
- The OC4J applications are using JAZN-LDAP to authenticate users, and in that case, the OID is accessed through the OID Load Balancer access point.
When looking at the error logs, following messages are found:
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |