Crowd does not fully support TimeBasedTriggeringPolicy

Issue Summary

Crowd does not fully support TimeBasedTriggeringPolicy
 

Steps to Reproduce

• Edit the below file -

  /crowd-webapp/WEB-INF/classes/applicationContext-CrowdBootstrap.xml
  

• Look for the below file -

  <property name="logFileName" value=
  

• Update the parameter to as below -

  <property name="logFileName" value="atlassian-crowd.log.%d{yyyy-MM-dd-HH}"/>
  

  

• Now, edit the below file -

  /crowd-webapp/WEB-INF/classes/log4j2.properties
  

• Look for the below files -

  appender.crowdlog.policies.size.type=SizeBasedTriggeringPolicy
  appender.crowdlog.policies.size.size=20480KB
  

• Replace the above lines with the below and save the changes -

  appender.crowdlog.policies.time.type=TimeBasedTriggeringPolicy
  appender.crowdlog.policies.time.interval=1
  appender.crowdlog.policies.time.modulate=true
  

• Note - appender.crowdlog.policies.time.interval=1 defines a number of hrs, so if you want to rotate the logs every 01 hrs set the value to 1 and if you want to rotate every 06 hrs then set the value to 6
• Start Crowd and application should come up.

The problem is that in the logs you will see the log pattern as atlassian-crowd.log.%d {yyyy-MM-dd-HH}.1 The .1 at the end, which is never defined in any conf file and it seems like default behaviour as it just adds it to the file with no pattern which is not expected.

Expected Results

The Crowd logging should be like

crowd.log.%d\{yyyy-MM-dd-HH}

Actual Results

The current Crowd log is -

Crowd.log.%d{yyyy-MM-dd-HH}.1

Workaround

Currently, there is no known workaround for this behaviour. A workaround will be added here when available