Question
Atos Syntel
IN
Last activity: 21 Jan 2016 12:10 EST
DailyRollingFileAppenderPega is not working in PRPC 7.1.5
Hi,
i found the below link few days ago where different types of appenders have been mentioned.
https://community.pega.com/sites/default/files/help_v719/procomhelpmain.htm
I tried using DailyRollingFileAppenderPega in the prlogging.xml of 7.1.7 version, it worked fine there but when i try it in 7.1.5 version i get the following error during application startup.
Is the appender only available in versions 7.1.7 and above ?
i have also attached the prlogging.xml file for reference.
Jan 06, 2016 5:02:10 AM com.pega.pegarules.internal.bootstrap.phase2.PRBootstrapImpl
INFO: PRAppLoader jar path entry = /xjp/tomcat/apache-tomcat-7.0.42/work/Catalina/localhost/efi/extractedFiles/apploader
Jan 06, 2016 5:02:10 AM com.pega.pegarules.internal.bootstrap.PRBootstrap
19830421:
============ PegaRULES Bootstrap Configuration ============
Date: Wed Jan 06 05:02:10 EST 2016
Java Version: Oracle Corporation 1.7.0_21
Configuration: file:/xjp/tomcat/apache-tomcat-7.0.42/webapps/efi/WEB-INF/classes/prbootstrap.properties
Pega-EngineCode: 07-10-11
ASM Version: 72822592
Hi,
i found the below link few days ago where different types of appenders have been mentioned.
https://community.pega.com/sites/default/files/help_v719/procomhelpmain.htm
I tried using DailyRollingFileAppenderPega in the prlogging.xml of 7.1.7 version, it worked fine there but when i try it in 7.1.5 version i get the following error during application startup.
Is the appender only available in versions 7.1.7 and above ?
i have also attached the prlogging.xml file for reference.
Jan 06, 2016 5:02:10 AM com.pega.pegarules.internal.bootstrap.phase2.PRBootstrapImpl
INFO: PRAppLoader jar path entry = /xjp/tomcat/apache-tomcat-7.0.42/work/Catalina/localhost/efi/extractedFiles/apploader
Jan 06, 2016 5:02:10 AM com.pega.pegarules.internal.bootstrap.PRBootstrap
19830421:
============ PegaRULES Bootstrap Configuration ============
Date: Wed Jan 06 05:02:10 EST 2016
Java Version: Oracle Corporation 1.7.0_21
Configuration: file:/xjp/tomcat/apache-tomcat-7.0.42/webapps/efi/WEB-INF/classes/prbootstrap.properties
Pega-EngineCode: 07-10-11
ASM Version: 72822592
Database: Oracle Oracle Database 11g Enterprise Edition Release Proprietary information hidden.0 - 64bit Production
With the Partitioning option
Driver: Oracle JDBC driver Proprietary information hidden.0
Active CodeSets: snowslides:01-01-01 at (latest patch)
pdfbox:01-01-01 at (latest patch)
mq:01-01-01 at (latest patch)
snowwoodstox:01-01-01 at (latest patch)
snowlog4j:01-01-01 at (latest patch)
snowcells:01-01-01 at (latest patch)
snowstax2:01-01-01 at (latest patch)
snowwords:01-01-01 at (latest patch)
snowdom4j:01-01-01 at (latest patch)
sftp:01-01-01 at (latest patch)
customer:06-01-01 at (latest patch)
pega-enginecode:07-10-11 at (latest patch)
fofjxl:01-01-01 at (latest patch)
snow:01-01-01 at (latest patch)
fontbox:01-01-01 at (latest patch)
ups:01-01-01 at (latest patch)
=============== End Bootstrap Configuration ===============
Current "user.dir" (default directory) is: /xjp/utility/pegahome
Located PegaRULES logging configuration: file:/xjp/utility/pegahome/prlogging.xml
log4j:ERROR Could not create an Appender. Reported error follows.
java.lang.ClassNotFoundException: com.pega.pegarules.priv.util.DailyRollingFileAppenderPega
at com.pega.pegarules.bootstrap.loader.PRAppLoader.loadClass(PRAppLoader.java:773)
at com.pega.pegarules.bootstrap.loader.PRAppLoader.loadClass(PRAppLoader.java:634)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:188)
at com.pega.apache.log4j.helpers.Loader.loadClass(Loader.java:209)
at com.pega.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:212)
at com.pega.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:166)
at com.pega.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:179)
at com.pega.apache.log4j.xml.DOMConfigurator.parseAppender(DOMConfigurator.java:253)
at com.pega.apache.log4j.xml.DOMConfigurator.findAppenderByName(DOMConfigurator.java:166)
at com.pega.apache.log4j.xml.DOMConfigurator.findAppenderByReference(DOMConfigurator.java:179)
at com.pega.apache.log4j.xml.DOMConfigurator.parseChildrenOfLoggerElement(DOMConfigurator.java:467)
at com.pega.apache.log4j.xml.DOMConfigurator.parseRoot(DOMConfigurator.java:436)
at com.pega.apache.log4j.xml.DOMConfigurator.parse(DOMConfigurator.java:922)
at com.pega.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:796)
at com.pega.apache.log4j.xml.DOMConfigurator.doConfigure(DOMConfigurator.java:723)
at com.pega.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:507)
at com.pega.apache.log4j.LogManager.initializeConfig(LogManager.java:163)
at com.pega.pegarules.priv.LogHelper._initLogging_privact(LogHelper.java:671)
at com.pega.pegarules.priv.LogHelper.init(LogHelper.java:655)
at com.pega.pegarules.priv.LogHelper.<init>(LogHelper.java:268)
at com.pega.pegarules.web.servlet.WebAppLifeCycleListener._contextInitialized_privact(WebAppLifeCycleListener.java:199)
at com.pega.pegarules.web.servlet.WebAppLifeCycleListener.contextInitialized(WebAppLifeCycleListener.java:174)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:419)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:460)
at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:509)
at com.pega.pegarules.internal.web.servlet.WebAppLifeCycleListenerBoot.contextInitialized(WebAppLifeCycleListenerBoot.java:83)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4939)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5434)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:633)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:656)
at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1635)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
at java.util.concurrent.FutureTask.run(FutureTask.java:166)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:722)
Accepted Solution
I do not believe that is possible in 7.1.5 simply by configuring prlogging.xml. The logs can roll daily, however, there is no way to set a limit to the number that are created. You could do this and then create a batch or script on your OS that can clean up old files in the log directory.
If I'm remembering correctly, the only way to control the number of log files created in 7.1.5 would be to roll the logs based on size. This will allow you to specify a "MaxBackupIndex".
For example:
I do not believe that is possible in 7.1.5 simply by configuring prlogging.xml. The logs can roll daily, however, there is no way to set a limit to the number that are created. You could do this and then create a batch or script on your OS that can clean up old files in the log directory.
If I'm remembering correctly, the only way to control the number of log files created in 7.1.5 would be to roll the logs based on size. This will allow you to specify a "MaxBackupIndex".
For example:
<appender name="PEGA" class="com.pega.apache.log4j.RollingFileAppender"> <param name="File" value="'PegaRULES.log'"/>
<param name="MaxFileSize" value="5KB"/>
<param name="MaxBackupIndex" value="10"/>
<layout class="com.pega.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d{ABSOLUTE} [%20.20t](%30.30c{3}) %-5p %X{stack} %X{userid} - %m%n"/>
</layout>
</appender>
This will roll logs based on size, generating log files PegaRULES.log, PegaRULES.log.1, PegaRULES.log.2, and so on. The log file with no number will contain the latest log entries, and as the number increases, the older the log entries will be. In the example above, the oldest entries will be in, "PegaRULES.log.10" once enough log files have been created to reach the 10th file.
The value of MaxFileSize can be changed to suit the requirement (100KB, 10MB, etc.). This will only create logs until the MaxBackupIndex value is reached. Once this is reached, the oldest entries will start to be lost.
Atos Syntel
IN
Is it the same case for FileAppenderPega, RollingFileAppenderPega and DailySizeRollingFileAppenderPega ?
I can see the com.pega.pegarules.priv.util.FileAppenderPega appender referenced in the prlogging.xml of PRPC 6.3 and 7.1.5 installation packages that i got from Pega few months ago.
Pegasystems Inc.
IN
This stands true for RollingFileAppenderPega and DailySizeRollingFileAppenderPega.
However, for FileAppenderPega, I believe, it is there in PRPC 7.1.5 as well.
You can check about this in pr_engineclasses of PRPC 7.1.5 schema or in prpublic.jar
Atos Syntel
IN
I found a relevant class in the pr_engineclasses table called - PegaDailyRollingFileAppender
do you know this ?
if yes, please share the parameters for this appender.
Pegasystems Inc.
IN
Per my understanding , this class is no more available and has been renamed to DailyRollingFileAppenderPega in PRPC 7.1.7
I think , PegaDailyRollingFileAppender was just a local override for https://bz.apache.org/bugzilla/show_bug.cgi?id=29726
Atos Syntel
IN
Didn't find any help in Bug 29726 – DailyRollingFileAppender : log4j:ERROR Failed to rename
Raising an SR to know the parameters of PegaDailyRollingFileAppender.
Pegasystems Inc.
US
Please let us know the SR number once you raise it so that we may track it here in your thread as well. This way it also lets the Engineers know to come to the Community to see any/all troubleshooting that has occurred already so they don't duplicate efforts.
Yeah i agree with Nicholas. Its not necessary that using "PegaDailyRollingFileAppender" appender would help. Can you explain the exact use case or the expected outcome from the appender?
Atos Syntel
IN
I need an appender which will roll out Pega log files daily.
I need to keep only last 30 days of backup logs.
backup logs that are older that 30 days should get automatically deleted.
Accepted Solution
I do not believe that is possible in 7.1.5 simply by configuring prlogging.xml. The logs can roll daily, however, there is no way to set a limit to the number that are created. You could do this and then create a batch or script on your OS that can clean up old files in the log directory.
If I'm remembering correctly, the only way to control the number of log files created in 7.1.5 would be to roll the logs based on size. This will allow you to specify a "MaxBackupIndex".
For example:
I do not believe that is possible in 7.1.5 simply by configuring prlogging.xml. The logs can roll daily, however, there is no way to set a limit to the number that are created. You could do this and then create a batch or script on your OS that can clean up old files in the log directory.
If I'm remembering correctly, the only way to control the number of log files created in 7.1.5 would be to roll the logs based on size. This will allow you to specify a "MaxBackupIndex".
For example:
<appender name="PEGA" class="com.pega.apache.log4j.RollingFileAppender"> <param name="File" value="'PegaRULES.log'"/>
<param name="MaxFileSize" value="5KB"/>
<param name="MaxBackupIndex" value="10"/>
<layout class="com.pega.apache.log4j.PatternLayout">
<param name="ConversionPattern" value="%d{ABSOLUTE} [%20.20t](%30.30c{3}) %-5p %X{stack} %X{userid} - %m%n"/>
</layout>
</appender>
This will roll logs based on size, generating log files PegaRULES.log, PegaRULES.log.1, PegaRULES.log.2, and so on. The log file with no number will contain the latest log entries, and as the number increases, the older the log entries will be. In the example above, the oldest entries will be in, "PegaRULES.log.10" once enough log files have been created to reach the 10th file.
The value of MaxFileSize can be changed to suit the requirement (100KB, 10MB, etc.). This will only create logs until the MaxBackupIndex value is reached. Once this is reached, the oldest entries will start to be lost.