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

Tomcat server does not shut down

SA-8487

Summary



While stopping with Tomcat server that is hosting PRPC application, it is taking longer time duration (45 minutes) to stop the process.
Pega class 'com.pega.pegarules.data.internal.access.Saver’ debug log shows that query updates are taking longer time to complete.
Also Catalina.out file shows that the shutdown process is complete, but PRPC application needs to be stopped.

Error Messages



Not Applicable.

Steps to Reproduce



Use shutdown.sh script to stop the server and notice the time taken to completely stop the server.

Root Cause



Enable debug for the pega class 'com.pega.pegarules.data.internal.access.Saver’.
During the PRPC engine shutdown sequence, it writes the rule usage statistics to database table pr4_log_rule_usage.

Resolution




For this issue, tuning the database performance improves the shutdown time duration by 60% [45 minutes to 15 minutes]
 
Suggest Edit

Published June 12, 2015 - Updated December 2, 2021

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