prlog4j2 not printing logs to PegaRULES.log, PegaRULES-ALERT.log
After upgrading from 7.2.0 to 7.4 we converted prlogging.xml to prlog4j2.xml.
This is what we have for the PegaRULES portion. The path used for filename is local to the server but even then we cannot get any logs to print. SR-C58590 was opened for this but no problems were able to be discovered so far. Any ideas? Thank you.
<RollingRandomAccessFile name="PEGA" fileName="/srv/ao/logs/WSDPGAA001A1/pega/PegaRULES.log" filePattern="/srv/ao/logs/WSDPGAA001A1/pega/PegaRULES-%d{MM-dd-yyyy}-%i.log.gz">
<PatternLayout>
<Pattern>%d [%20.20t] [%10.10X{pegathread}] [%20.20X{tenantid}] [%20.20X{app}] (%30.30c{3}) %-5p %X{stack} %X{userid} - %m%n</Pattern>
</PatternLayout>
<Filters>
<!--Deny message logged under ALERT log level-->
<ThresholdFilter level="ALERT" onMatch="DENY" onMismatch="NEUTRAL"/>
</Filters>
<Policies>
<TimeBasedTriggeringPolicy />
<SizeBasedTriggeringPolicy size="250 MB"/>
</Policies>
<DefaultRolloverStrategy max="20"/>
</RollingRandomAccessFile>
***Moderator Edit-Vidyaranjan: Updated SR details***
Accepted Solution
Auto-Owners Insurance
US
We discovered the problem with this last week. There was a URL resource on the WAS side called PegaLoggingConfig we forgot about. This needed to be updated to use "prlog4j2.xml" in its path instead of "prlogging.xml". Once we corrected the URL resource and restarted servers the problem was resolved. Thank you Kavitha for your previous response.
Ucare
US
We had similar sceanrio after upgrade from 717 to 731 and when I created an SR, the support tech identiifed that the prweb.war was not upgraded to 731.So they told us to repalce teh prweb.war file from the pega exe which you might run for the pega upgrade(update) and remove the already exisiting prweb folder alogn with prweb.war. after doing that , we cleared the marker file adn on restart the logger worked for us.May be this solution may work for you as I am not sure about your scenario.
Accepted Solution
Auto-Owners Insurance
US
We discovered the problem with this last week. There was a URL resource on the WAS side called PegaLoggingConfig we forgot about. This needed to be updated to use "prlog4j2.xml" in its path instead of "prlogging.xml". Once we corrected the URL resource and restarted servers the problem was resolved. Thank you Kavitha for your previous response.