Support Article
Application does not boot post WebLogic upgrade
SA-105579
Summary
Post WebLogic 12.2.1.3 upgrade, on restarting the Pega application after deployment, unable to access the application and an error occurs on booting the Application server.
Error Messages
[fault (self-tuning)'] [ ] [ ] [ ] (ternal.store.DataSourceManager) ERROR - Unable to obtain DataSource for pegadata; javax.naming.NameNotFoundException: Unable to resolve 'jdbc.AdminPegaRules'. Resolved 'jdbc'; remaining name 'AdminPegaRules'
[fault (self-tuning)'] [ ] [ ] [ ] (dbms.JdbcConnectionManagerImpl) ERROR - Failed to read Data-Admin-DB-Name Definitions: Database-BadDBDef-Missing Unable to obtain DataSource object
[fault (self-tuning)'] [ ] [ ] [ ] (ervlet.WebAppLifeCycleListener) ERROR - Exception during startup processing
com.pega.pegarules.pub.PRRuntimeException: Error determining the mode of PRPC install from database.
Steps to Reproduce
- Upgrade WebLogic 12.2.1.2 to WebLogic 12.2.1.3.
- Deploy the application.
- Restart the application.
Root Cause
When WebLogic was upgraded, the JNDI name associated with the data source changed. The plan.xml displayed the JNDI name incorrectly.
Resolution
Edit the plan.xml to have the correct data source JNDI name associated with the PegaRULES and PegaDATA data sources.
Published April 14, 2020 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.