Skip to main content

When to restart an application server

Suggest edit Updated on October 18, 2021

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 Required: System changes

Restart Required: Symptoms and errors

Examples of symptoms and errors

Post to the Product Support Community

Restart not needed


Read Application release changes, types, and processes.

To know when to restart your non-production tiers in your Pega Cloud environment, see
Restarting your non-production environments.

Restart Required: System changes

Restart the application server when you have made the following changes to your system.

Types of system changes that require restarting the application server

Change Target


Application serverAny change to the application server, for example, changing the properties of a JDBC connection
ApplicationChanging the system name
Configuration files

Any changes to web.xml, prconfig.xml, or to Dynamic System Settings (DSS), for example

  • Updating web.xml files to create new authentication service URL
  • System settings in the prconfig.xml file
  • Dynamic System Settings (DSS) updates that get loaded at system startup
  • Schema changes applied outside of a Product rule of Rule-Admin-Product class (RAP) migration
  • Exposed columns or new tables created and not found
  • Reconfigured database access or addition of another container-managed database resource
  • Rolling upgrade of the application or environment using schema snapshots rather than a RAP migration
  • RAP import with custom JAR files
  • Hotfixes installed that affect Engine classes
  • Newly loaded custom or third-party JAR files
  • MBean properties

Restart Required: Symptoms and errors

When you encounter the symptoms and errors listed in this section, take two actions:

  1. Restart the application server.
  2. Post to the Product Support Community.

Examples of symptoms and errors

  • 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

Post to the Product Support Community

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

Restart not needed

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.
Did you find this content helpful? YesNo

93% found this useful

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. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us