Support Article
Pega on WAS has startup issue due to JNDI naming for data source
SA-20136
Summary
Brand new jvm not starting up with new settings
Startup log attached
Error Messages
[2/5/16 9:30:30:196 CST] 00000012 PRBootstrapDa E com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource Unable to obtain DataSource for java:comp/env/jdbc/PegaRULES; com.ibm.websphere.naming.CannotInstantiateObjectException: A NameNotFoundException occurred on an indirect lookup on the name java:comp/env/jdbc/PegaRULES. The name java:comp/env/jdbc/PegaRULES maps to a JNDI name in deployment descriptor bindings for the application performing the JNDI lookup. Make sure that the JNDI name mapping in the deployment descriptor binding is correct. If the JNDI name mapping is correct, make sure the target resource can be resolved with the specified name relative to the default initial context. [Root exception is javax.naming.NameNotFoundException: Context: cjs1stl24MCPega7_cell/clusters/BPMS_MMA_Cluster, name: jdbc/PegaRULES: First component in name PegaRULES not found. [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:/CosNaming/NamingContext/NotFound:1.0]]
[2/5/16 9:30:30:207 CST] 00000012 PRBootstrap Z com.pega.pegarules.internal.bootstrap.PRBootstrap Engine schema defined in allclasses: null
[2/5/16 9:30:30:210 CST] 00000012 SettingReader Z com.pega.pegarules.internal.bootstrap.SettingReaderJNDI Could not find java:comp/env/prconfig/ in the local JNDI context, skipping prconfig setting lookup
[2/5/16 9:30:30:213 CST] 00000012 SettingReader Z com.pega.pegarules.internal.bootstrap.SettingReaderJNDI Could not find prconfig in the local JNDI context, skipping prconfig setting lookup
[2/5/16 9:30:30:215 CST] 00000012 PRBootstrap Z com.pega.pegarules.internal.bootstrap.PRBootstrap Engine classes schema: null
[2/5/16 9:30:30:218 CST] 00000012 PRBootstrap Z com.pega.pegarules.internal.bootstrap.PRBootstrap Assembled classes schema: null
Steps to Reproduce
Restart jvm.
Root Cause
A software use or operation error.
From environment screenshot ----> jdbc:oracle:thin:@(DESCRIPTION
Resolution
Perform the following local-change:
1.) Changed the JNDI name on the Data Source to jdbc/PegaRULES (follow case)?
2.) Corrected the URL :
From install guide : Specify a URL for the Type 4 (thin client) JDBC driver jdbc:oracle:thin:@<server_name>:1521:<myDatabase>
Published February 23, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.