Monday, January 3, 2011

MDS-00054 when starting up SOA Suite 11g


Apparently, one of our developers tried to deploy some SOA code to our Oracle SOA Suite 11g ( environment, and midway through the deployment, the server crashed. The code was not fully deployed.

Every time we tried to start up the "soa_server1", we received the following error in the "soa_server1.out" log file, and we were unable to bring up the server:
<Dec 28, 2010 7:12:58 PM EST> <Error> <HTTP> <BEA-101216> <Servlet:
"FabricInit" failed to preload on startup in Web application: "/soa-infra".
oracle.fabric.common.FabricException: Error in getting XML input stream:
  oracle.mds.exception.MDSException: MDS-00054: The file to be loaded
  does not exist.

1. Manually create an "adf-config.xml" file, with a format similar to the following, replacing highlighted values with your  database settings for the MDS.
<?xml version="1.0" encoding="windows-1252" ?>
<adf-config xmlns="" xmlns:adf="">
  <adf:adf-properties-child xmlns="">
    <adf-property name="adfAppUID" value="TemporaryMDS-2296"/>
  <adf-mds-config xmlns="">
    <mds-config xmlns="">
          <namespace metadata-store-usage="mstore-usage_1" path="/apps"/>
          <namespace metadata-store-usage="mstore-usage_1" path="/deployed-composites"/>
          <namespace metadata-store-usage="mstore-usage_1" path="/soa"/>
          <metadata-store-usage id="mstore-usage_1">
            <metadata-store class-name="oracle.mds.persistence.stores.db.DBMetadataStore">
              <property value="DEV_MDS" name="jdbc-userid"/>
              <property value="welcome1" name="jdbc-password"/>
              <property value="jdbc:oracle:thin:@//oradev:1521/orcl" name="jdbc-url"/>
              <property value="soa-infra" name="partition-name"/>
2. Copy the "adf-config.xml" file to your server, particularly in the location where your half-deployed project exists. The directory location will be something like this:
3. Restart "soa_server1"

Additional Information:

As a note, while we were troubleshooting this issue, we encountered these exceptions as well, which are probably related to the root cause above.
<Dec 28, 2010 11:33:26 AM EST> <Notice> <WebLogicServer> <BEA-000330> <Started WebLogic Managed Server "soa_server1" for domain "soa_domain" running in Production Mode>
Exception in thread "TimerFactory" java.lang.NoClassDefFoundError: oracle/bpel/services/workflow/task/impl/WorkflowTimerAgent
at java.util.TimerThread.mainLoop(
Caused by: java.lang.ClassNotFoundException:
at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(
at weblogic.utils.classloaders.GenericClassLoader.findClass(
at java.lang.ClassLoader.loadClass(
at java.lang.ClassLoader.loadClass(
at weblogic.utils.classloaders.GenericClassLoader.loadClass(
... 4 more

<Dec 28, 2010 12:02:27 PM EST> <Warning> <> <BEA-000000> <<.> Error while setting task display, this can happen with app loading issue, trying to load for 17> javax.naming.NameNotFoundException: Unable to resolve 'RuntimeConfigService'. Resolved ''; remaining name 'RuntimeConfigService'
at sun.reflect.GeneratedMethodAccessor1639.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
at java.lang.reflect.Method.invoke(
at $Proxy311.setTaskDisplayInfo(Unknown Source)
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'RuntimeConfigService'. Resolved ''; remaining name 'RuntimeConfigService'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(
at weblogic.jndi.internal.BasicNamingNode.lookupHere(
at weblogic.jndi.internal.ServerNamingNode.lookupHere(
at weblogic.jndi.internal.BasicNamingNode.lookup(
at weblogic.jndi.internal.WLEventContextImpl.lookup(
at weblogic.jndi.internal.WLContextImpl.lookup(
at javax.naming.InitialContext.lookup(
... 10 more

Applicable Versions:
  • Oracle SOA Suite 11g (

1 comment:

Anonymous said...

Ahmed, 2 node RAC instance (2 node RAC on both PRIMARY and STANDBY with passive dataguard between PRIMARY and STANDBY). What is the best way to make this work when the database has been switched over and the app is now connected to MDS on the STANDBY database? Any suggestions appreciated. SOA version is Thanks