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

Pega failed to start after upgrade from 7.1.9 to 7.2

SA-20272

Summary



JBoss EAP 6.3.3.GA was used as application server to upgrade from Pega 7.1.9 to Pega 7.2. Errors related to application deployment occurred in JBoss server.log.

Error Messages



276 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014775:    New missing/unsatisfied dependencies:      service jboss.naming.context.java.jdbc.AdminPegaRULES (missing) dependents:
.
.
.

Steps to Reproduce



1. Install Pega 7.2 using JBoss EAP 6.3.3.GA as application server.
2. Start the server, and watch logs.

Root Cause



AdminPegaRULES datasource is mandatory in case of JBoss deployments for Pega 7.2.

Resolution



Make the following change to the operating environment:

Define the AdminPegaRULES datasource and the JNDI bindings.

Refer to Pega 7.2 Platform Installation Guide for JBoss and MSSQL available in PDN for more information;
https://pdn.pega.com/documents/pega-72-platform-installation-guide-jboss-and-mssql
Suggest Edit

Published February 26, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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