My Oracle Support Banner

OAM Failover Test Failing with "java.lang.NoClassDefFoundError: Could not initialize class org.owasp.esapi.reference.DefaultValidator" Error (Doc ID 2063992.1)

Last updated on DECEMBER 12, 2017

Applies to:

Oracle Access Manager - Version to [Release 11g]
Information in this document applies to any platform.


Oracle Access Manager (OAM) BP04 ( with one-off patch 20813561

This is a Multi Data Center (MDC) environment but issue can be reproduced on non-MDC environments. (ie just a Master/Clone environment can reproduce the issue).

Primary(Master) OAM Cluster server instances(oam_server1, oam_server2) are pointing to SCAN database.
Secondary(Clone) OAM Cluster instances(oam_server1,oam_server2) are pointing to standalone database instance.

Problem Summary
OAM Failover Test failing with the following error:

<[ServletContext@1208077712[app:oam_server module:oam path:/oam spec-version:2.5 version:]] Root cause of ServletException.
java.lang.NoClassDefFoundError: Could not initialize class org.owasp.esapi.reference.DefaultValidator
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(
at org.owasp.esapi.util.ObjFactory.make(
at org.owasp.esapi.ESAPI.validator(
Truncated. see log file for complete stacktrace

Issue is only observed under load testing.



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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.