My Oracle Support Banner

Unable to start WebLogic after Config.xml changes (Doc ID 2729783.1)

Last updated on NOVEMBER 18, 2020

Applies to:

Oracle Financial Services Analytical Applications Infrastructure - Version 8.0.7 and later
Information in this document applies to any platform.

Symptoms



On : 8.0.7 version, Metadata_OFSS

When attempting to start WebLogic
the following error occurs.

ERROR
-----------------------
nohup.out
--------------

1. weblogic.management.provider.internal.RuntimeAccessImpl$SchemaValidationException: [Management:141245]Schema validation error in /u02/oracle/domains/FCCMdomain/config/config.xml. See the log for details. Schema validation can be disabled by starting the server with the command line option: -Dweblogic.configuration.schemaValidationEnabled=false.
2. java.lang.IllegalStateException: Unable to perform operation: create on weblogic.management.provider.internal.RuntimeAccessImpl
3. java.lang.IllegalStateException: Unable to perform operation: post construct on weblogic.management.provider.internal.RuntimeAccessService

A MultiException has 3 exceptions. They are:
1. weblogic.management.provider.internal.RuntimeAccessImpl$SchemaValidationException: [Management:141245]Schema validation error in /u02/oracle/domains/FCCMdomain/config/config.xml. See the log for details. Schema validation can be disabled by starting the server with the command line option: -Dweblogic.configuration.schemaValidationEnabled=false.
2. java.lang.IllegalStateException: Unable to perform operation: create on weblogic.management.provider.internal.RuntimeAccessImpl
3. java.lang.IllegalStateException: Unable to perform operation: post construct on weblogic.management.provider.internal.RuntimeAccessService

at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:392)
at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:487)
at org.jvnet.hk2.internal.SingletonContext$1.compute(SingletonContext.java:83)
at org.jvnet.hk2.internal.SingletonContext$1.compute(SingletonContext.java:71)
at org.glassfish.hk2.utilities.cache.Cache$OriginThreadAwareFuture$1.call(Cache.java:97)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at org.glassfish.hk2.utilities.cache.Cache$OriginThreadAwareFuture.run(Cache.java:154)
at org.glassfish.hk2.utilities.cache.Cache.compute(Cache.java:199)
at org.jvnet.hk2.internal.SingletonContext.findOrCreate(SingletonContext.java:122)
at org.jvnet.hk2.internal.Utilities.createService(Utilities.java:2126)
at org.jvnet.hk2.internal.ServiceLocatorImpl.internalGetService(ServiceLocatorImpl.java:777)
at org.jvnet.hk2.internal.ServiceLocatorImpl.getUnqualifiedService(ServiceLocatorImpl.java:789)


Caused By: weblogic.management.provider.internal.RuntimeAccessImpl$SchemaValidationException: [Management:141245]Schema validation error in /u02/oracle/domains/FCCMdomain/config/config.xml. See the log for details. Schema validation can be disabled by starting the server with the command line option: -Dweblogic.configuration.schemaValidationEnabled=false.
at weblogic.management.provider.internal.RuntimeAccessImpl.processSchemaErrors(RuntimeAccessImpl.java:359)
at weblogic.management.provider.internal.RuntimeAccessImpl.parseNewStyleConfig(RuntimeAccessImpl.java:279)
at weblogic.management.provider.internal.RuntimeAccessImpl.(RuntimeAccessImpl.java:144)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)



STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Try to start Weblogic

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot access the application deployed on WebLogic

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
References


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