Cannot Deploy OAM Policy To Oracle API Gateway Instance - "Error: java.lang.NoClassDefFoundError: com/vordel/el/SelectorString"
(Doc ID 1918268.1)
Last updated on OCTOBER 07, 2022
Applies to:
Oracle API Gateway - Version 11.1.2.2.0 and laterInformation in this document applies to any platform.
Symptoms
Oracle API Gateway 11.1.2.2.0 does not deploy a policy with OAM sdk components.
The patch for defect 17973629 has been applied to the environment.
The jvm.xml has been updated as per the instructions in the patch:
<ClassPath name="<OAG HOME>/apigateway/ext/lib/com.vordel.circuit.oracle_asdk.jar" />
<Environment name="ASDK_HOME" value="<ASDK_HOME>" />
<ClassDir name="$ASDK_HOME" />
<VMArg name="-Doracle.security.jps.config=$ASDK_HOME/config/jps-config.xml" />
...
<Environment name="ASDK_HOME" value="<ASDK_HOME>" />
<ClassDir name="$ASDK_HOME" />
<VMArg name="-Doracle.security.jps.config=$ASDK_HOME/config/jps-config.xml" />
...
The error being seen in the trace file is the following:
java.lang.NoClassDefFoundError: com/vordel/el/SelectorString
at com.vordel.circuit.oracle.AccessManagerProcessor.filterAttached(AccessManagerProcessor.java:26)
at com.vordel.circuit.oracle.AccessManagerProcessor.filterAttached(AccessManagerProcessor.java:26)
NOTE: Substitute the OAG_HOME and ASDK_HOME for the actual values in the installation.
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 |
References |