Unable To Start Admin Server After Editing Config.xml File
(Doc ID 2791399.1)
Last updated on APRIL 01, 2022
Applies to:
Oracle E-Business Suite Technology Stack - Version 12.2 to 12.2 [Release 12.2]Information in this document applies to any platform.
Symptoms
Admin Servers are not running from both RUN/PATCH file systems.
Below is the error reported in admin server log file.
<Jul 8, 2021 5:39:08 PM AST> <Error> <Management> <BEA-141244> <Schema validation errors while parsing $FMW_HOME/user_projects/domains/EBS_do
main/config/config.xml - Element 'security-configuration@http://xmlns.oracle.com/weblogic/domain' with element-only content type cannot have text content.>
<Jul 8, 2021 5:39:08 PM AST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: [Management:141245]Schema Validation Error in $FMW_HOME/user_projects/domains/EBS_domain/config/config.xml see log for details. Schema validation can be disabled by starting the server with the command line o
ption: -Dweblogic.configuration.schemaValidationEnabled=false>
<Jul 8, 2021 5:39:08 PM AST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Jul 8, 2021 5:39:08 PM AST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Jul 8, 2021 5:39:08 PM AST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<Jul 8, 2021 5:39:08 PM> <FINEST> <NodeManager> <Waiting for the process to die: 73685>
<Jul 8, 2021 5:39:08 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Jul 8, 2021 5:39:08 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
....
Changes
Modified the config.xml file to update the connection filter rules.
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 |