com.pega.pegarules.pub.context.InitializationFailedError: PRNodeImpl init failed

BhanuPrakash_G · March 15, 2022, 10:43am

We are seeing the below error when we hit the pega url.

HTTP Status 503 – Service Unavailable.

Pega logs has the following error. Any help is highly appreciated.

Exception in thread “StartupTaskUtil INITIALIZE_QUEUE_PROCESSORS” java.lang.StackOverflowError
at com.pega.pegarules.exec.internal.util.SpecializerImpl.getInternationalVariants(SpecializerImpl.java:139)
at com.pega.pegarules.exec.internal.util.SpecializerImpl.specialize(SpecializerImpl.java:69)
at com.pega.pegarules.exec.internal.util.RSLSpecializerImpl.getSpecializedList(RSLSpecializerImpl.java:75)
at com.pega.pegarules.exec.internal.basic.RulesetListImpl.applySpecializations(RulesetListImpl.java:1080)
at com.pega.pegarules.exec.internal.basic.RulesetListImpl.initialize(RulesetListImpl.java:780)
at com.pega.pegarules.exec.internal.basic.ApplicationRulesetListImpl.(ApplicationRulesetListImpl.java:97)
at com.pega.pegarules.exec.internal.basic.ApplicationRulesetListImpl.duplicate(ApplicationRulesetListImpl.java:171)
at com.pega.pegarules.exec.internal.basic.StaticRulesetListImpl.getReadOnlyList(StaticRulesetListImpl.java:506)
at com.pega.pegarules.exec.internal.basic.StaticRulesetListImpl.getReadOnlyList(StaticRulesetListImpl.java:474)
at com.pega.pegarules.session.internal.authorization.context.LegacyContext.getRuleSetList(LegacyContext.java:310)
at com.pega.pegarules.session.internal.authorization.Authorization.getRuleSets(Authorization.java:669)
at com.pega.pegarules.data.internal.access.DatabaseImpl.open(DatabaseImpl.java:2625)
at com.pega.pegarules.data.internal.access.DatabaseImpl.open(DatabaseImpl.java:2595)
at com.pega.pegarules.exec.internal.basic.StaticRulesetListImpl.doesRuleSetNameExist(StaticRulesetListImpl.java:404)
at com.pega.pegarules.exec.internal.util.SpecializerImpl.doesRuleSetNameExist(SpecializerImpl.java:241)
at com.pega.pegarules.exec.internal.util.SpecializerImpl.getInternationalVariants(SpecializerImpl.java:164)
at com.pega.pegarules.exec.internal.util.SpecializerImpl.specialize(SpecializerImpl.java:69)
at com.pega.pegarules.exec.internal.util.RSLSpecializerImpl.getSpecializedList(RSLSpecializerImpl.java:75)
at com.pega.pegarules.exec.internal.basic.RulesetListImpl.applySpecializations(RulesetListImpl.java:1080)
at com.pega.pegarules.exec.internal.basic.RulesetListImpl.initialize(RulesetListImpl.java:780)
at com.pega.pegarules.exec.internal.basic.ApplicationRulesetListImpl.(ApplicationRulesetListImpl.java:97)
at com.pega.pegarules.exec.internal.basic.ApplicationRulesetListImpl.duplicate(ApplicationRulesetListImpl.java:171)
at com.pega.pegarules.exec.internal.basic.StaticRulesetListImpl.getReadOnlyList(StaticRulesetListImpl.java:506)
at com.pega.pegarules.exec.internal.basic.StaticRulesetListImpl.getReadOnlyList(StaticRulesetListImpl.java:474)
at com.pega.pegarules.session.internal.authorization.context.LegacyContext.getRuleSetList(LegacyContext.java:310)
at com.pega.pegarules.session.internal.authorization.Authorization.getRuleSets(Authorization.java:669)
at com.pega.pegarules.data.internal.access.DatabaseImpl.open(DatabaseImpl.java:2625)
at com.pega.pegarules.data.internal.access.DatabaseImpl.open(DatabaseImpl.java:2595)
at com.pega.pegarules.exec.internal.basic.StaticRulesetListImpl.doesRuleSetNameExist(StaticRulesetListImpl.java:404)
at com.pega.pegarules.exec.internal.util.SpecializerImpl.doesRuleSetNameExist(SpecializerImpl.java:241)
at com.pega.pegarules.exec.internal.util.SpecializerImpl.getInternationalVariants(SpecializerImpl.java:164)
at com.pega.pegarules.exec.internal.util.SpecializerImpl.specialize(SpecializerImpl.java:69)
at com.pega.pegarules.exec.internal.util.RSLSpecializerImpl.getSpecializedList(RSLSpecializerImpl.java:75)
at com.pega.pegarules.exec.internal.basic.RulesetListImpl.applySpecializations(RulesetListImpl.java:1080)
at com.pega.pegarules.exec.internal.basic.RulesetListImpl.initialize(RulesetListImpl.java:780)
at com.pega.pegarules.exec.internal.basic.ApplicationRulesetListImpl.(ApplicationRulesetListImpl.java:97)
at com.pega.pegarules.exec.internal.basic.ApplicationRulesetListImpl.duplicate(ApplicationRulesetListImpl.java:171)
at com.pega.pegarules.exec.internal.basic.StaticRulesetListImpl.getReadOnlyList(StaticRulesetListImpl.java:506)
at com.pega.pegarules.exec.internal.basic.StaticRulesetListImpl.getReadOnlyList(StaticRulesetListImpl.java:474)
at com.pega.pegarules.session.internal.authorization.context.LegacyContext.getRuleSetList(LegacyContext.java:310)
at com.pega.pegarules.session.internal.authorization.Authorization.getRuleSets(Authorization.java:669)
at com.pega.pegarules.data.internal.access.DatabaseImpl.open(DatabaseImpl.java:2625)
at com.pega.pegarules.data.internal.access.DatabaseImpl.open(DatabaseImpl.java:2595)
at com.pega.pegarules.exec.internal.basic.StaticRulesetListImpl.doesRuleSetNameExist(StaticRulesetListImpl.java:404)
at com.pega.pegarules.exec.internal.util.SpecializerImpl.doesRuleSetNameExist(SpecializerImpl.java:241)

BhanuPrakash_G · March 17, 2022, 5:54am

Appreciate if anyone can provide pointers in debugging the issue.

BhanuPrakash_G · March 23, 2022, 6:31am

Still looking for help

PoojaGadige · March 23, 2022, 7:28am

Hello @Prakash

Did you check out this post or this post or this post?

BhanuPrakash_G · March 23, 2022, 7:50am

@PoojaGadige Have gone through the articles but none of them have been able to rectify the issue.

BhanuPrakash_G · March 23, 2022, 9:54am

@MarijeSchillern Thank you for the response. We did a fresh installation of Pega 8.5.2 few weeks ago and everything was work fine (were able to login and do our work) but few days ago when we try to login we are seeing a “HTTP Status 503 – Service Unavailable” and unable to login.

Attaching the full log file for your reference. Appreciate your help.

Thank you.

ErrorLog.txt (195 KB)

BhanuPrakash_G · March 23, 2022, 11:54am

@MarijeSchillern Thank you for your time in responding to my question. As suggested have opened

	INC-214541

MarijeSchillern · April 13, 2022, 4:22pm

I have checked support ticket INC-214541 and notice that our support team had to close it due to lack of response.

Below the troubleshooting guidelines which were suggested to you.

Our Cassandra team notice the following in your previous logs:

Detected powershell execution permissions. Running with enhanced startup scripts.

WARNING! Automatic page file configuration detected.
It is recommended that you disable swap when running Cassandra
for performance and stability reasons.

WARNING! Detected a power profile other than High Performance.
Performance of this node will suffer.
Modify conf\cassandra.env.ps1 to suppress this warning.

VerifyPortsAreAvailable : Found a port already in use. Aborting startup

Analysis:

As the DDS runs on 9042 and the error says the “Found a port already in use. Aborting startup At C:\Program Files\Apache Software Foundation\Tomcat 9.0_PegaCOE\cassandra\bin\cassandra.ps1:98 char:9”.

check if any firewall is enabled that prevents port 9042 from communicating.
Check with your network team whether there are connections on this server to port 9042?

As the port that DDS use is not available you are getting this. you can check "VerifyPortsAreAvailable :

TCP <removed IP details>
SYN_SENT" and 9042.

You were asked to verify the below link

Configuring firewall port access

As you are an on-premise client you were asked to check the above comments with your network team.

Note that without the full debug logs the support team were not be able to help further therefore the case is closed.

MarijeSchillern · March 23, 2022, 9:32am

@Prakash Do you just see errors in the logs, or do users experience application issues?

Can you confirm if this is a new install?

Has there been a DB migration or other similar change?

What is the platform stack you are using?

The error extract you provided includes reference to “INITIALIZE_QUEUE_PROCESSORS”.

During system startup “system runtime context(SRC)” will form and loads all the QP rules according to SRC with the given QP configurations where it will read this alert threshold also to raise the alerts appropriately when ever after system startup.

what is the java version used at your end and also JAVA_Home and path variable are set properly?

Can you check the context.xml and prconfig.xml to cross check DB info .

add below to prconfig file with your own cluster name and try:

prconfig/identification/cluster/name.

And PFB the reference for contect.xml configuration:

<Environment name=“url/initialization/explicittempdir” value=
<Environment name=“prconfig/database/databases/PegaRULES/defaultSchema” value=
<Environment name=“prconfig/database/databases/PegaDATA/defaultSchema” value=

Can you check this post Cannot access pega designer studio after apply changes on prconfig.xml and verify the context.xml entries?

If you need a more in-depth help analyzing your full logs, please can we ask that you log a support incident?

Please provide the INC id here so that we can help you track it.

MarijeSchillern · March 23, 2022, 11:23am

@Prakash

I see Authorization errors.

Also:

Caused by: com.pega.pegarules.pub.PRRuntimeException: Method Invocation exception
	at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1401) ~[prprivate-session.jar:?]

Caused by: java.lang.reflect.InvocationTargetException

Caused by: com.pega.pegarules.pub.PRRuntimeException: Startup Task: [INITIALIZE_QUEUE_PROCESSORS] has failed after retries or with error
	at com.pega.pegarules.session.internal.async.startup.StartupTaskUtil.awaitStartupTasks(StartupTaskUtil.java:145) ~[prprivate-session.jar:?]
	at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1399) ~[prprivate-session.jar:?]
	... 57 more

Caused by: java.lang.**StackOverflowError**
	at com.pega.pegarules.pub.context.ThreadContainer.get(ThreadContainer.java:66) ~[prpublic.jar:?]

I’m wondering if there’s a problem with the URL.

Can you please check the DSS settings listed in the following article?

I think it would be best if you engage a support engineer to go into a more in-depth help analysis of your logs.

Please can we ask that you log a support incident?

Please provide the INC id here so that we can help you track it.

MarijeSchillern · March 23, 2022, 12:03pm

@Prakash many thanks, I’ve added the ticket id to this post and we will track this in parallel to allow other users to benefit once the issue is identified by our support team.

Conversation		Replies	Views
HTTP Status 503 – Service Unavailable while connecting to my pega host General pega-platform , system-administration , installation-and-deployment	2	389	April 26, 2024
Could not initialize services of type [StreamServer] General pega-platform , system-administration , updates	6	1606	March 15, 2021
Pega 24.2 Log - com.pega.pegarules.internal.bootstrap.PRBootstrap General pega-platform , java-and-activities	3	110	December 17, 2024
PEGA 8.8.3 Not Starting General senior-system-architect , system-architect , system-administration , updates , installation-and-deployment , performance , financial-services , 8-8-3	4	348	May 4, 2023
Pega startup fails post 7.x to 8.7.3 upgrade General consulting-solution-executive , system-administration , case-management , data-integration , updates , insurance , 8-7-3	3	214	December 6, 2022

com.pega.pegarules.pub.context.InitializationFailedError: PRNodeImpl init failed

Related topics