When to restart an application server
Knowing when you need to stop and restart the application server (bounce the system) for your Pega deployment saves you time and effort. Especially if you are using the Pega Cloud, you can reduce the number of support requests you submit to request an application server restart. Sometimes you might think that you need to restart the application server when there is no need to do so.
Restart the application server when you have made the following changes to your system.
|Application server||Any change to the application server, for example, changing the properties of a JDBC connection|
|Application||Changing the system name|
Any changes to web.xml, prconfig.xml, or to Dynamic System Settings (DSS), for example
When you encounter the symptoms and errors listed in this section, take two actions:
- Restart the application server.
- Post to the Product Support Community.
- Wrong rule running and erratic system pulse, for example
- System pulse is suspected of not keeping rules synchronized across nodes.
- Pulse fails to pick up or apply a rule change on one or more nodes.
- Rule resolution or rule cache issues appear in a multi-node deployment or on a single node (unknown causes related to system pulse).
- Hung threads
- Thread dumps that can cause system performance issues
- Out of memory errors
- Static content errors
- Failure to regenerate a Rule-Utility-Function (RUF) or Rule-Utility-Library (RUL) after a RAP import
- Looping rules running rampant
- Rule caching issues, for example, a higher version is available, but is not found (development server)
- Static cache issue causing the user interface (images, icons, other elements controlled by the CSS) to not display correctly
If you experience a symptom or error that you cannot resolve, post a question describing your scenario to the Pega Product Support Community.
Posting to the community is the best way to expedite root cause analysis and resolution of your issues.
After you post your question to the community, Pega Global Customer Support (GCS) engineers can determine if you need to submit a Support Request (SR).
Your problem scenario might be caused by any one of the following reasons that require an SR:
- A defect in Pegasystems’ code or rules
- A defect or configuration issue in the operating environment
- A software use or operation error
- An installation, upgrade, or migration failure
- Another reason
Some common misperceptions exist.
You do not need to stop and restart the application server in the following situations:
- When deploying new rules
- When deploying rule-only hotfixes
- After changing the prlogging.xml file
You can run the activity Code-RefreshLogConfiguration to process changes at system startup.
See this Product Support Community post, Implementing changes to prlogging.xml without restarting.