Pega 8.5.6 shuts down after start up on its own.

General
, , ,
1

We are running on-prem Pega 8.5.6 on WebLogic 12.2.1 with Oracle 19c. The server starts up fine then shuts down on its own with few minutes without giving any indication of why. Has anyone faced similar issue before? Some inputs would be appreciated.

Thanks

Atanu

2

@AtanuS17

Can you share the PegaRULES.log logfile? thank you

3

@shanp

The logs are attached to INC-262745 or please share your email I will forward. Thanks.

4

@AtanuS17 Based on my Pega experience, unexpected shutdowns of a Pega server can be caused by a variety of factors, including issues with the server infrastructure, application configuration, or database connectivity. In your specific case, the fact that the server starts up fine but then shuts down on its own after a few minutes without any indication of why could indicate that the issue is related to the server infrastructure or application configuration.

One potential cause could be a memory leak in the application or server infrastructure, which could cause the server to crash after running for a certain period of time. Another potential cause could be a misconfiguration in the server settings, such as incorrect values for timeouts or memory limits, which could cause the server to shut down unexpectedly.

In my personal experience, I have seen a similar issue with a Pega server that was caused by an issue with the database connectivity. In this case, the server would start up and run fine for a while, but then suddenly crash without any clear indication of why. After investigating the issue, we found that the issue was related to a misconfiguration in the database settings, which was causing the server to lose its connection to the database and crash.

To resolve the issue, we reviewed and updated the database settings to ensure that they were configured correctly. We also implemented a monitoring system to track server performance and detect any potential issues before they could cause the server to crash.

Based on my experience and expertise, I would suggest that you check the server logs for any error messages or indications of the cause of the issue. It may also be helpful to review and update the server and application settings to ensure that they are configured correctly. Additionally, implementing a monitoring system can help to detect any potential issues before they can cause the server to crash.

5

I can see from INC-262745 that the issue was resolved.

The investigation suggested the following:

  1. Add following entry in your prconfig.xml file

  2. Save your prconfig.xml file

  3. Attempt to start Pega and let me know about results

If that approach does not work, could you please provide with additional information to help us understand this issue better:

  1. prconfig.xml file after performing mentioned modifications
  2. PegaRULES and PegaRULES-ALERT logs from fresh reproduction of this issue
  3. details of solution implemented in (INC-261963) System not starting up after upgrade : 8.5.1 → 8.8.0 which was withdrawn with “Reason: Resolved the issue myself.”
  4. details on recent changes performed on this environment (as you have mentioned that SSL certs were changed but then reverted back).
  5. confirmation on Java version used by running the following command in terminal:
    java -version

The solution for this issue was listed as Case withdrawn. Reason: SSL certificate issue