• One of our customers reported that after setting a cron policy from log4j.properties to rotate every minute, the artemis.log file remained empty.
   
• Env:
     - AMQ 7.11.6
   
  -Here are the steps to reproduce the issue:
    - Create a broker instance with ./artemis create command. Do not allow anonymous access.
    - Change within log4j2.properties the artemis log file pattern and its cron policy to have the file rotate upon a minute.
    - Start the broker instance with ./artemis run
    - Once you notice the artemis log file has rotated, from another window, run an  /artemis producer command with a wrong password. 
• cron policy:
    - appender.log_file.policies.cron.schedule = 0 * * * * ? * attaching the log4j2.properties file for reference. - log4j2.properties

• Problem: 

  - We may loss some logging details. 

  - The logs are visible in the artemis console (CLI) but not getting printed in artemis.log file.