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

llegalStateException occurs while opening application instance



Post upgrade to Pega 7.4, IllegalStateException occurs while opening a specific instance of an application rule. This occurs for every version of the application rule.

Error Messages

[WebContainer : 3] [TABTHREAD1] [ ] [an_app:xx.yy.zz] (ngineinterface.service.HttpAPI) ERROR|a_host an_operator - a_host PRRuntimeError
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivitiesAlt( ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.runActivitiesAlt( ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.runActivities( ~[prprivate.jar:?]
at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequestInner( ~[prenginext.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0-internal]
at sun.reflect.NativeMethodAccessorImpl.invoke( ~[?:1.8.0-internal]
at sun.reflect.DelegatingMethodAccessorImpl.invoke( ~[?:1.8.0-internal]
Caused by: java.lang.IllegalStateException
at ~[prprivate.jar:?]
at com.pega.pegarules.deploy.internal.appconfig.AppConfigKey.getConfigurationPage( ~[prprivate.jar:?]
at com.pega.pegarules.deploy.internal.appconfig.AppConfigFetcher.findApplicationOfConfiguration( ~[prprivate.jar:?]
at com.pega.pegarules.deploy.internal.appconfig.AppConfigFetcher.fetch( ~[prprivate.jar:?]
at com.pega.pegarules.deploy.internal.appconfig.populate.AppConfigValuesPopulator.populate( ~[prprivate.jar:?]
at com.pega.pegarules.deploy.internal.appconfig.AppConfigManagerImpl.populateConfigurations( ~[prprivate.jar:?]

Steps to Reproduce

  1. Update from Pega 7.2 to Pega 7.4.
  2. Open an application created in a Pega 7.2 and which contains ':' character in the Application ID field on a Pega 7.4 system.

Root Cause

In Pega 7.4, the system prevents the creation of the application containing ':' character in the Application ID field through validation. However, this restriction does  not exist in Pega 7.2. When a system is upgraded from Pega 7.2 to Pega 7.4, the Application Rule created in Pega 7.2 can contain characters that are invalid in Pega 7.4 and thus resulting in the error.


Create a fresh application without the special character that adheres to the Pega 7.4 validation.


Published September 27, 2018 - Updated December 2, 2021

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