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.

Issue: Must restart application server after database server restart

Suggest edit Updated on September 13, 2021

Summary

If the database server hosting the PegaRULES database fails, you must stop and restart the application server after the database server is back up, to reestablish the database connection

Update: This issue is addressed in V4.2.  Beginning with V4.2, a Process Commander restart is no longer necessary after a database server problem.


 

 

Suggested Approach

V4.1 keeps a pool of database connections, and when one of these connections fails (the database server goes down, or some other database problem occurs), errors occur when the next database operation is attempted (saves, updates, etc.). 

After the database problems have been handled, and the database is back in operation, restarting Process Commander reestablishes the connection to the database, allowing commits and other database processing. 

Process Commander does not automatically reinitiate a connection during the next system pulse.

 

Tags

Pega Platform 7.1.1 - 8.3.1 Business Architect System Architect System/Cloud Ops Administrator System Administration
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us