Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

4
Replies
153
Views
 PRADEEP CHOWDARY PYDI (PradeepPydi) Anthem Senior PEGA DEVOPS and Cloud Administrator
Anthem
US
PradeepPydi Member since 2017 239 posts
Anthem
Posted: December 27, 2018
Last activity: March 8, 2019
Posted: 27 Dec 2018 15:38 EST
Last activity: 8 Mar 2019 11:44 EST
Closed
Solved

PEGA errors stack in the tomcat logs.

Report

Hi Team,

We could find lots of PEGA Rules exceptions or PEGA errors stack in the tomcat logs.

Any idea to rectify please ?

PFA for the tomcat log.

Thank you.

***Edited by Moderator Marissa to update SR Details***

System Administration Support Case Created
Posted: 4 years ago
Posted: 2 Jan 2019 9:59 EST
Arvind Malav (malaa) Technical Manager
Pegasystems Inc.
IN
Report

Request you to raise Product SR with Support so that it can be investigated by an expert.

Accepted Solution

Posted: 4 years ago
Posted: 8 Mar 2019 11:43 EST
Marissa Rogers (MarissaRogers) MOD Senior Knowledge Management Specialist
Pegasystems Inc.
US
Report

Upon reviewing the associated SR, the resolution was as follows:

Update prlog4j2.xml "CONSOLE" block to onMismatch="DENY", as bolded:

<Console name="CONSOLE" target="SYSTEM_OUT">
<PatternLayout pattern="%d [%20.20t] [%10.10X{pegathread}] [%20.20X{tenantid}] [%20.20X{app}] (%30.30c{3}) %-5p %X{stack} %X{userid} - %m%n"/>
<Filters>
<!--Deny message logged under ALERT log level-->
<ThresholdFilter level="ALERT" onMatch="DENY" onMismatch="DENY"/>
</Filters>
</Console>

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice