Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Prbootstrap not found in jndi context - prweb not started

SA-31953

Summary



The user cannot start the application. Errors are thrown: Could not find java:comp/env/prbootstrap/ in the local JNDI context, skipping prconfig setting lookup

DB: PostgreSQL 94

App server Tomcat 7.0.69-10

Error Messages



Unable to obtain DataSource for pegadata; javax.naming.NameNotFoundException: Name [AdminPegaRULES] is not bound in this Context. Unable to find [AdminPegaRULES].


Could not find java:comp/env/prbootstrap/ in the local JNDI context, skipping prconfig setting lookup

2016-12-22 17:00:32,809 [ocalhost-startStop-1] [ ] [ ] [ ] (ion.internal.PRGenProviderImpl) INFO - invokeDynamic instrumentation for inlining is enabled
2016-12-22 17:00:32,809 [ocalhost-startStop-1] [ ] [ ] [ ] (ion.internal.PRGenProviderImpl) INFO - Assembly Version: -415794285
2016-12-22 17:00:33,343 [ocalhost-startStop-1] [ ] [ ] [ ] (ernal.access.DataSourceManager) ERROR - Unable to obtain DataSource for pegadata; javax.naming.NameNotFoundException: Name [AdminPegaRULES] is not bound in this Context. Unable to find [AdminPegaRULES].
2016-12-22 17:00:33,351 [ocalhost-startStop-1] [ ] [ ] [ ] (ervlet.WebAppLifeCycleListener) ERROR - Exception during startup processing
com.pega.pegarules.pub.PRRuntimeException: Error determining the mode of PRPC install from database.
at com.pega.pegarules.data.internal.PRDataProviderImpl.isMultiTenantEnvironment(PRDataProviderImpl.java:1145)
at com.pega.pegarules.deploy.internal.archive.ParUtilsImpl.setStageDirectory(ParUtilsImpl.java:213)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineStartup.initEngine(EngineStartup.java:513)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl._initEngine_privact(EngineImpl.java:172)
at com.pega.pegarules.session.internal.engineinterface.etier.impl.EngineImpl.doStartup(EngineImpl.java:145)
at com.pega.pegarules.web.servlet.WebAppLifeCycleListener._contextInitialized_privact(WebAppLifeCycleListener.java:311)
at com.pega.pegarules.web.servlet.WebAppLifeCycleListener.contextInitialized(WebAppLifeCycleListener.java:218)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)


Steps to Reproduce



Install Pega with below Enviornment:

DB: PostgreSQL 94

App server Tomcat 7.0.69-10

with Data Admin user specified in context.xml


Root Cause



The error message is clear: There are expected resource references for logical name "jdbc/AdminPegaRULES" that are not provided.


Resolution



Here is what we need to do (for the admin datasource)

Add below in the context.xml for Tomcat. Similar approach can be done for other servers.


<Resource name="jdbc/AdminPegaRULES"
auth="Container"
type="javax.sql.DataSource"
driverClassName="oracle.jdbc.OracleDriver"
url="jdbc:oracle:thin:@vengwindb234:1521:prpcgcs"
username="v717stadmin"
password="xxxxxx"
maxActive="50"
maxIdle="30"
maxWait="10000"
/>

<Environment name="prconfig/database/databases/PegaRULES/dataSourceAdmin" value="java:comp/env/jdbc/AdminPegaRULES" type="java.lang.String"/>

<Environment name="prconfig/database/databases/PegaDATA/dataSourceAdmin" value="java:comp/env/jdbc/AdminPegaRULES" type="java.lang.String"/>

Published February 28, 2017 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us