Question
Requirement of JVM recycle after a product installation
Hi,
1. May I please know under what circumstances are we supposed to recycle the JVM servers after an install?
2. What are the rules which actually demand for a server recycle after the installation in production environment?
Thank you
Mayank Jain
***Updated by moderator: Lochan to add Category***
Thanks for replying. We are also following this as a best practice in our system however I am wondering if there are some recommendations from Pega on this.
This may depend on your version of the software and exactly what is in your product file.
Normally my expectation is that most rule changes will be picked up automatically. Furthermore, this should coordinate those rule updates across the other application servers that are connected to your database instance.
But, just to qualify, I'm most frequently working with Pega 7 product versions.
If your product file includes jar files (classes) and an earlier version of that class is already loaded on the system, then I believe you may need to restart the application server to get it to load the new version of the class.
Hi Mayak,
Usually JVM restart doent require every code move, because systempulse agent taking for sync those change between the JVMs.
We see some rule type(ex, binary file, static content) not effecting after the product migration, during that time need to clean the temp and restart JVM.
Please let me know, this will helps you.
Regards,
Anandh
Hi Mayank,
As per my knowledge, Ideally server restart is required when there are rule changes happened due to installation.
To assemble new rules or to reassemble existing rule(which might be in cache), a JVM restart with clearing of temp files including PegaRULES_extract_marker.txt file is suggested.