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 NOVEMBER 15, 2016

Applies to:

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

Symptoms

Environment:
----------------
Oracle Access Manager (OAM) BP04 (11.1.2.2.4) 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:11.1.2.0.0]] 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(Class.java:190)
at org.owasp.esapi.util.ObjFactory.make(ObjFactory.java:74)
at org.owasp.esapi.ESAPI.validator(ESAPI.java:191)
at oracle.security.am.common.utilities.esapi.impl.ESAPIImpl.getValidInput(ESAPIImpl.java:161)
Truncated. see log file for complete stacktrace

Issue is only observed under load testing.

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms