Version:
WLS: 10.3.6
ADF: 11.1.1.6.0
Issue:
Issues on starting MDS data source when wsm-pm is deployed in to a Managed server. The Managed server startup was failing.
The Managed server startup log had following inforation
Feb 04, 2014 7:54:33 AM oracle.adf.share.config.ADFMDSConfig parseADFConfiguration
SEVERE: MDS Configuration Exception encountered in parse ADF ConfigurationMDS-01330: unable to load MDS configuration document
MDS-01329: unable to load element "persistence-config"
MDS-01370: MetadataStore configuration for metadata-store-usage "OWSM_TargetRepos" is invalid.
MDS-00929: unable to look up name "jdbc/mds/owsm" in JNDI context
javax.naming.NameNotFoundException: While trying to lookup 'jdbc.mds/owsm' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/mds/owsm'
Caused By: oracle.mds.exception.MDSExceptionList: MDS-01329: unable to load element "persistence-config"
MDS-01370: MetadataStore configuration for metadata-store-usage "OWSM_TargetRepos" is invalid.
MDS-00929: unable to look up name "jdbc/mds/owsm" in JNDI context
javax.naming.NameNotFoundException: While trying to lookup 'jdbc.mds/owsm' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/mds/owsm'
at oracle.mds.config.PConfig.loadFromBean(PConfig.java:1020)
at oracle.mds.config.PConfig.<init>(PConfig.java:775)
at oracle.mds.config.MDSConfig.loadFromBean(MDSConfig.java:1254)
at oracle.mds.config.MDSConfig.loadFromElement(MDSConfig.java:1326)
at oracle.mds.config.MDSConfig.<init>(MDSConfig.java:884)
Truncated. see log file for complete stacktrace
Action:
We can verify couple of this to make sure the setup done is correct
1. The "wsm-pm" deployment should only be targeted to the managed server. If it has Admin server also, uncheck it from its deployment target.
2. Another reason and possible reason if the wsm-pm only has Managed server as its target is when the JDBC data source mds-owsm is not targeted to the managed server. Add the Managed server to its target list.
Note: Also in Fusion Middleware 12c Infrastructure, we might have to add the data source opss-data-source also as a target to the Managed Server to access wsm-pm URL properly.
WLS: 10.3.6
ADF: 11.1.1.6.0
Issue:
Issues on starting MDS data source when wsm-pm is deployed in to a Managed server. The Managed server startup was failing.
The Managed server startup log had following inforation
Feb 04, 2014 7:54:33 AM oracle.adf.share.config.ADFMDSConfig parseADFConfiguration
SEVERE: MDS Configuration Exception encountered in parse ADF ConfigurationMDS-01330: unable to load MDS configuration document
MDS-01329: unable to load element "persistence-config"
MDS-01370: MetadataStore configuration for metadata-store-usage "OWSM_TargetRepos" is invalid.
MDS-00929: unable to look up name "jdbc/mds/owsm" in JNDI context
javax.naming.NameNotFoundException: While trying to lookup 'jdbc.mds/owsm' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/mds/owsm'
Caused By: oracle.mds.exception.MDSExceptionList: MDS-01329: unable to load element "persistence-config"
MDS-01370: MetadataStore configuration for metadata-store-usage "OWSM_TargetRepos" is invalid.
MDS-00929: unable to look up name "jdbc/mds/owsm" in JNDI context
javax.naming.NameNotFoundException: While trying to lookup 'jdbc.mds/owsm' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/mds/owsm'
at oracle.mds.config.PConfig.loadFromBean(PConfig.java:1020)
at oracle.mds.config.PConfig.<init>(PConfig.java:775)
at oracle.mds.config.MDSConfig.loadFromBean(MDSConfig.java:1254)
at oracle.mds.config.MDSConfig.loadFromElement(MDSConfig.java:1326)
at oracle.mds.config.MDSConfig.<init>(MDSConfig.java:884)
Truncated. see log file for complete stacktrace
Action:
We can verify couple of this to make sure the setup done is correct
1. The "wsm-pm" deployment should only be targeted to the managed server. If it has Admin server also, uncheck it from its deployment target.
2. Another reason and possible reason if the wsm-pm only has Managed server as its target is when the JDBC data source mds-owsm is not targeted to the managed server. Add the Managed server to its target list.
Note: Also in Fusion Middleware 12c Infrastructure, we might have to add the data source opss-data-source also as a target to the Managed Server to access wsm-pm URL properly.
