DB Adapter calls using the Agent are failing at runtime with "Could not initialize class org.apache.xmlbeans.XmlBeans"
(Doc ID 2872541.1)
Last updated on SEPTEMBER 28, 2022
Applies to:
Oracle Integration - Version 17.4.1 and laterInformation in this document applies to any platform.
Symptoms
Database Adapter calls (eg. invoking a SQL or Stored Procedure) are failing with:
java. util. concurrent.ExecutionException: java.lang.NoClassDefFoundError: Could not initialize class org.apache.xmlbeans.XmlBeans :Application Error
The Adapter Connection test works, but at runtime the Integration invokes fail with:
"title" : "Internal Server Error"
"detail" : "Internal server error. Please contact oracle support for details. " ,
"errorCode" : 500"
"errorDetai1s" : [ {
"type" : "UnmappedFau1t:getMyProc_REQUEST",
"instance" : "NA
"title" . "java. util. concurrent.ExecutionException: java.lang.NoClassDefFoundError:
Could not initialize class org.apache.xmlbeans.XmlBeans :App1ication Error",
"errorpath" : "NA",
"errorCode" : "NA"
}]
"detail" : "Internal server error. Please contact oracle support for details. " ,
"errorCode" : 500"
"errorDetai1s" : [ {
"type" : "UnmappedFau1t:getMyProc_REQUEST",
"instance" : "NA
"title" . "java. util. concurrent.ExecutionException: java.lang.NoClassDefFoundError:
Could not initialize class org.apache.xmlbeans.XmlBeans :App1ication Error",
"errorpath" : "NA",
"errorCode" : "NA"
}]
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 |
Cause |
Solution |