Unable to set crontriggeringpolicy for log4j2

Solution Verified - Updated -

Issue

  • Below is my setting in "org.ops4j.pax.logging.cfg", but it failed to function.
  • It seems the crontriggeringpolicy and schedule not working, since no log file remain the same.
# Using cron
log4j2.appender.analytics3.type = RollingRandomAccessFile
log4j2.appender.analytics3.name = analytics3
log4j2.appender.analytics3.fileName = ${karaf.data}/log/analytics3.log
log4j2.appender.analytics3.filePattern = ${karaf.data}/log/analytics3_%d{yyyy-MM-dd-HH-mm}.log
log4j2.appender.analytics3.append = true
log4j2.appender.analytics3.layout.type = PatternLayout
log4j2.appender.analytics3.layout.pattern = ${log4j2.pattern}
log4j2.appender.analytics3.policies.type = Policies
log4j2.appender.analytics3.policies.cron.type = CronTriggeringPolicy
log4j2.appender.analytics3.policies.cron.schedule = "0 0/1 * * * ? *"
log4j2.appender.analytics3.strategy.type = DefaultRolloverStrategy
log4j2.appender.analytics3.strategy.max = 7

Environment

  • Red Hat Fuse
    • 7.4.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content