Contributed by Andrzej Adamczyk and Prathamesh Kirloskar
Symptom
Errors
Explanations
Environments
Solutions
Symptom
In various scenarios, your Pega deployment fails to start or restart. You see the error InvalidApplicationReferenceException: No such Rule-Application instance: <rule application name and ruleset> or other exceptions identified in Errors.
Scenarios in which this problem occurs include the following situations:
After updating your Pega deployment to a newer release and starting Deployment Manager, you cannot access a staging environment. In Deployment Manager, you see the error Fail: Unexpected HTTP 500 Response code. When you try to access the staging environment, you see the browser error An error has occurred processing this request - java.lang.RuntimeException : Problem during method invocation (doPostInner).
Your self-service restart of a development test environment from My Pega Cloud fails.
You have deployed changes to your STG1 and STG2 environments. The changes in STG1 environment work as expected, but the changes in the STG2 environment do not. You notice that the latest rules are not being used during the run time for the application. To resolve this problem, you first deployed the application using Deployment Manager. Then you deployed the application manually. These attempts failed to resolve the problem. Further investigation is needed into your STG2 environment.
You migrate your Pega deployment from an on-premises environment to a Pega Cloud® services environment. After you migrate the rules, you change the system name to the name used in the on-premises environment. After this system name change, application users cannot access the login screen and they see the error Caused by: com.pega.pegarules.pub.context.InvalidApplicationReferenceException: No such Rule-Application instance: Rulereference_<rule reference>.
When you try to start your Pega deployment, in the staging environment, you see the error 503: PegaRULES server not available. After you recycle the JVM, the error persists in the system log:
00000409 webapp E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: [Servlet Error]-[WebStandard]: com.ibm.ws.webcontainer.webapp.WebAppErrorReport: PegaRULES server not available at com.ibm.ws.webcontainer.webapp.WebAppDispatcherContext.sendError(WebAppDispatcherContext.java:637) at com.ibm.ws.webcontainer.webapp.WebAppDispatcherContext.sendError(WebAppDispatcherContext.java:667) at com.ibm.ws.webcontainer.srt.SRTServletResponse.sendError(SRTServletResponse.java:1308) at com.pega.pegarules.web.impl.WebStandardImpl.addErrorToResponse(WebStandardImpl.java:1591)
When trying to restart My Pega Cloud, you cannot log in to the environment and you see the errors. The prpc:agents and prpc:asyncprocessor access groups were moved from the Pega Platform version 7.x system to a cloud environment.
Errors
InvalidApplicationReferenceException: No such Rule-Application:<rule:ruleset version>
Unexpected HTTP 500 Response code
java.lang.RuntimeException : Problem during method invocation (doPostInner)
Explanations
Invalid product migration causes system failure at startup. This is one of the common symptoms related to Pega engine startup issues. When a Requestor access group is configured with a missing Application rule, the Errors result on system startup attempts. See Solutions, Pega Defect Correction.
User configuration errors
The following examples were documented in cases reporting the problem. All of these configuration errors are a variant of an Application record having a missing component application because the system name prpc had been changed.
A required application is not present in the environment.
You imported the Application package with the wrong ruleset version.
A requestor instance used an access group that referred to an Application record that included a missing component application because the system name prpc had been changed.
Requestor instance refers to an access group that did have a reference to an Application record.
The access group defined in the environment’s browser instance refers to an application that contained a Rulereference_<rule reference> as a component application. However, this application was not migrated from the on-premises environment to the cloud environment.
The My Pega Cloud restart failed after access groups were migrated from the Pega Platform™ version 7.x system because the requestor instances mapped to the Unauthenticated access group were referencing PegaRULES 7.10 at the lowest level.
Environments
The problem was reported in the following environments:
- Pega Platform™ version 8.5.6 in Pega Cloud® services 2.23.2 and 2.24.10
- Pega Platform version 8.6.3 on-premises environment
- Pega Platform version 8.6.4 in Pega Cloud services 2.24.10
- Pega Platform version 8.6.5 on-premises environment
- Pega Platform version 8.6.6 in Pega Cloud services 2.24.10
- Pega Platform version 8.7.2 in Pega Cloud services 2.23-87
- Pega Platform version 8.7.3 in Pega Cloud services 2.24
- Pega Platform version 8.7.4 in Pega Cloud services 2.24.4
- Pega Platform version 8.8.1 on-premises environment
Solutions
Workaround
To recover from the Errors, you need to change the system name to prpc or pega, start the server, log in as administrator-at-pega.com, and correct the misconfiguration. Then revert the system name you used prior to changing it to prpc or pega and restart the server.
Perform this workaround by following these steps:
- To the file prconfig.xml, add the following environment name:
<env name="Identification/SystemName" value="prpc" />
Your system should start up as expected.
- Add the Application rule or ruleset back or remove the reference to the wrong Application rule.
- After you have added the correct application rule, remove the old entry from the file prconfig.xml.
Pega Defect Correction
Watch the Pega Support Center Pega Platform Resolved Issues and search for ISSUE-771196 in a future Pega Platform release.
Related content
Pega Documentation
Packaging your application in a product rule