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

Improve JVM start up time for Pega 7.1.8



Two nodes have an issue in JVM Start-up time. User would like to know whether DB fragmentation be done to improve the JVM start time.

Error Messages

Not Applicable.

Steps to Reproduce

Restart the JVM.

Root Cause

User was deleting the marker file which would cause roughly an additional 10-14 minutes to the startup time.  

Also user had min JDBC connection pool set to 1.  There is some db latency in addition to the above items such as pega0005s just over threshold.


Perform the following local-change steps:
  1. Do not delete the marker file unless code has been migrated or other rules imported.
  2. Increase minimum JDBC connection pool to 20. 


Published May 13, 2016 - 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