JMS Service Fails to Start Due To JDBCSTORE Deploy Error in a WebLogic Cluster if Server is not a Member of the Cluster (Doc ID 1214335.1)

Last updated on SEPTEMBER 26, 2016

Applies to:

Identity Manager - Version 9.1.0.1 and later
Information in this document applies to any platform.
**Checked for Relevance on 07-Sep-2013**

Symptoms

If OIM is deployed in a cluster on a manged server you can see the state of all of the servers and determine that the managed server is running.

However, in the error log for the managed server you find an error related to JMS similar to the following:

####<Sep 21, 2010 10:10:31 AM EDT> <Error> <Store> <ulbcenter-13-b04> <OIM_SERVER1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1285078231578> <BEA-280061> <The persistent store "OIM_SERVER1_OIM_JDBCSTORE" could not be deployed: weblogic.store.PersistentStoreException: Can't find JDBC DataSource jdbc/xlDS: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.xlDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/xlDS'
weblogic.store.PersistentStoreException: Can't find JDBC DataSource jdbc/xlDS: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.xlDS' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/xlDS'
  at weblogic.store.admin.JDBCAdminHandler.createDataSource(JDBCAdminHandler.java:107)
  at weblogic.store.admin.JDBCAdminHandler.makeStoreIO(JDBCAdminHandler.java:186)
  at weblogic.store.admin.JDBCAdminHandler.makeStore(JDBCAdminHandler.java:164)
  at weblogic.store.admin.JDBCAdminHandler.activate(JDBCAdminHandler.java:59)

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms