Servers are going in warning state and not visible in em console – SOA

Servers are going in warning state and not visible in em console -SOA

Weblogic Managed Servers are going in warning state and not visible in em console (SOA)-


<Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application ‘soa-infra’.


at weblogic.servlet.internal.WebAppModule.startContexts(

at weblogic.servlet.internal.WebAppModule.start(

at weblogic.application.internal.flow.ModuleStateDriver$

at weblogic.application.utils.StateMachineDriver.nextState(

at weblogic.application.internal.flow.ModuleStateDriver.start(

Truncated. see log file for complete stacktrace

Caused By: The cache configuration is missing: “$Domain_Home/custom-coherence-cache-config.xml”, loader=null







Check the path in  custom-coherence-cache-config.xml and tangosol-coherence-override.xml.  files are not placed properly in their respective location. If it is placed correctly, it can be xml format issue or a corrupted file.


Coherence configuration files are described in XML schemas (XSD). This file is used to specify the various types of caches which can be used within a cluster. This file is typically referred to as the cache configuration deployment descriptor. The schema for this file is the coherence-cache-config.xsd file.


Elements in the default tangosol-coherence.xml file are overridden by placing an operational override file named tangosol-coherence-override.xml in the classpath at run time. The structure of the override file and the operational deployment descriptor are the same except that all elements are optional. Any missing elements are loaded from the tangosol-coherence.xml file.

This override file is defined for the <coherence> root element and is used to override any element in the operational deployment descriptor. The root element in this file must be the <coherence> element.


For more such weblogic issues and resolution click here.

Latest Weblogic Interview Questions and Answers