My Oracle Support Banner

AdminServer Fails To Start After Extending The OSB Domain With Error "<WebLogicServer> <BEA-000362> <Server failed. Reason: [Management:141266]Parsing Failure in config.xml: " (Doc ID 2010910.1)

Last updated on APRIL 05, 2018

Applies to:

Oracle WebLogic Server - Version 11.1.1.6.0 and later
Information in this document applies to any platform.

Symptoms

You have extended an SOA domain to include the OSB cluster. Extending the domain was successful, but when you try to start the admin and managed servers, they are failing with a "Parsing Failure in config.xml" error:

<May 11, 2015 4:08:21 AM GMT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.5.0 Fri Apr 1 20:20:06 PDT 2011 1398638 >
<May 11, 2015 4:08:25 AM GMT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: [Management:141266]Parsing Failure in config.xml: weblogic.management.ManagementRuntimeException: weblogic.application.ModuleException: Could not create the JMS descriptor>
<May 11, 2015 4:08:25 AM GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<May 11, 2015 4:08:25 AM GMT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<May 11, 2015 4:08:25 AM GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>

 

Changes

Extended the domain to include an OSB cluster.

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


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