Server freezes during checkout rule

General
, , ,
1

We recently experienced a rather unfortunate issue, which we were unable to resolve on our own.
This issue has caused confusion within the management regarding update to newest versions.
The problem we are experiencing is that the server occasionally stops responding, requiring a reboot of Tomcat.
This issue can be triggered by two main factors: the checkout of a developer at the stand or the transfer of a branch to the stand via an archive.
Regardless of the scenario, the server’s behavior remains the same when certain pools are modified, such as sections or flows.
However, other rules do not typically present any issues. A single server is used instead of a cluster now.

There is an example of problem at 11:07-11:10 in attached logs.

PegaRULES-2024-Jun-12.log_.zip (2.13 MB)

2

@AlexanderK8875

I noticed this error in your logfile:

The following items were not serializable: [Property not serializable

Please check this discussion, which has a similar error message Error on logs - One or more properties could not be serialized during passivation and have therefore been lost. They will not be available on activation. Please ensure that all property data is Serializable | Support Center (pega.com)

It mentions one potential hotfix for this, for 7.2.2 (HFix-34508)

Is your system currently missing any hotfixes? Specifying the Hotfix Catalog location for Pega Hotfix Manager | Support Center

3

@PhilipShannon Thank you for anwer. This hotfix already exits. I attached hotfixes list

ScanResults_20240614T044825.288 GMT.zip (45.8 KB)

4

@PhilipShannon ,

I agree with you about that this is a serialization issue.
I have not seen any errors on the other stand and there have been no reboots.
There is hFIX-27261. Would it be worthwhile to request this?

5

@AlexanderK8875 I do not have any independent info on this except for the link that I posted earlier. Have you contacted Support for this issue yet?

6

@AlexanderK8875 I can see that you logged new support ticket INC-B26707 this week and you have recently provided GCS with the relevant log files for them to investigate.

Please keep us updated on this PSC forum post as well.

cc @PhilipShannon

7

@AlexanderK8875 INC-B26707 has been closed as our support team have not had a response since 8th July.

The final analysis was as follows:

Recommendation based on the log file content:-

Please use the below DSS setting and then perform the full cluster restart.

Purpose: SwitchToOldAssembler
Owning Ruleset: Pega-IntegrationEngine
Value: true

Predominantly, we suggest you to upgrade to latest Pega Infinity versions for more robust and flexible experience.

If you need further help, please contact the GCS team by using the ‘Reopen’ MSP ticket functionality.

cc @PhilipShannon