Support Article
Error occurs during startup after updating the custom appender
SA-67692
Summary
Error occurs during startup after updating the custom appender to use Log4J2 instead of the custom Log4J.
System configuration is as below:
- Tomcat 8.0.45
- PostgreSQL 9.4.14
- Oracle jvm 1.8.0_141
Error Messages
From Catalina log:
localhost-startStop-1 ERROR Error processing element appender ([Appenders: null]): CLASS_NOT_FOUND
localhost-startStop-1 ERROR Error processing element appender ([Appenders: null]): CLASS_NOT_FOUND
Unable to locate PegaRULES old logging configuration after trying:
<properties>
teuser-prlogging.xml
vapp-omcYAowV-prlogging.xml
prlogging.xml
Steps to Reproduce
- Update from Pega 7.2 to Pega 7.3.1
- Import the JAR file to the user codeset
- Replace server prlog4j2.xml with the JAR file's prlog4j2.xml or modify existing prlog4j2.xml accordingly to use the custom appender and point to a rule, for example, and activity, that can be executed
- Restart the server
- Execute the rule that is defined for the user's appender in prlog4j2.xml
Root Cause
A defect in Pegasystems’ code or rules.
Resolution
Perform the following local-change to enable the custom log appender on the user codeset: Add the custom appender jar to prweb/WEB-INF/lib directory.
If the requirement is to use the database, then add the Extract marker to the jar through the below steps:
- Open the jar with the custom Log4J appender (via 7zip)
- In the META-INF folder, add an empty 'pega.force.extract' file with the same name
- Import the jar file to the Pega application
- Clear the Pega temp directory and restart the server
Published August 19, 2019 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.