My Oracle Support Banner

Slow Managed Server Startup After 'Invalid MDS configuration specified in: "OWSM_TargetRepos"' Error (Doc ID 2240461.1)

Last updated on OCTOBER 21, 2021

Applies to:

Oracle SOA Suite - Version and later
Information in this document applies to any platform.


At managed server startup, there is an issue when deploying OWSM

[2017-03-01T13:12:37.041-08:00] [SOA3UAT_soa3_server1] [WARNING] [] [oracle.mds] [tid: [STANDBY].ExecuteThread: '4' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: OracleSystemUser] [ecid: aa5007b3-e9d6-4726-a39a-754e855227a4-0000000a,0] [APP: wsm-pm] [partition-name: DOMAIN] [tenant-name: GLOBAL] MDS-01367: Failed to create PConfig. Invalid MDS configuration specified in: "OWSM_TargetRepos" [[
oracle.mds.persistence.MDSIOException: MDS-00929: unable to look up name "jdbc/mds/owsm" in JNDI context
javax.naming.NameNotFoundException: Unable to resolve 'jdbc.mds.owsm'. Resolved 'jdbc.mds'; remaining name 'owsm'
at oracle.mds.internal.persistence.db.JNDIConnectionManagerImpl.inititializeDataSoureForNonMT(
at oracle.mds.internal.persistence.db.JNDIConnectionManagerImpl.initializeDataSources(
at oracle.mds.internal.persistence.db.JNDIConnectionManagerImpl.init(
at oracle.mds.internal.persistence.db.ConnectionManagerFactory.createConnectionManager(
Caused by: javax.naming.NameNotFoundException: Unable to resolve 'jdbc.mds.owsm'. Resolved 'jdbc.mds'; remaining name 'owsm'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(

This causes a slow server startup, due to subsequent frequent WSM-02311 and WSM-02302 errors because OWSM has not been correctly deployed.


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

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