Support Article
llegalStateException occurs while opening application instance
SA-60948
Summary
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 aa.bb.ccc.ddd|a_host an_operator - a_host com.pega.pegarules.pub.PRRuntimeError
com.pega.pegarules.pub.PRRuntimeError: PRRuntimeError
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivitiesAlt(ThreadRunner.java:712) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.runActivitiesAlt(PRThreadImpl.java:484) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.runActivities(HttpAPI.java:3467) ~[prprivate.jar:?]
at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequestInner(EngineAPI.java:417) ~[prenginext.jar:?]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0-internal]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) ~[?:1.8.0-internal]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55) ~[?:1.8.0-internal]
..........................
Caused by: java.lang.IllegalStateException
at com.pega.pegarules.data.internal.access.DatabaseImpl.getRulesetsFromApplication(DatabaseImpl.java:7012) ~[prprivate.jar:?]
at com.pega.pegarules.deploy.internal.appconfig.AppConfigKey.getConfigurationPage(AppConfigKey.java:136) ~[prprivate.jar:?]
at com.pega.pegarules.deploy.internal.appconfig.AppConfigFetcher.findApplicationOfConfiguration(AppConfigFetcher.java:125) ~[prprivate.jar:?]
at com.pega.pegarules.deploy.internal.appconfig.AppConfigFetcher.fetch(AppConfigFetcher.java:88) ~[prprivate.jar:?]
at com.pega.pegarules.deploy.internal.appconfig.populate.AppConfigValuesPopulator.populate(AppConfigValuesPopulator.java:88) ~[prprivate.jar:?]
at com.pega.pegarules.deploy.internal.appconfig.AppConfigManagerImpl.populateConfigurations(AppConfigManagerImpl.java:82) ~[prprivate.jar:?]
Steps to Reproduce
- Update from Pega 7.2 to Pega 7.4.
- 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.
Resolution
Create a fresh application without the special character that adheres to the Pega 7.4 validation.
Published September 27, 2018 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.