In AAI 6.5.4 some of the log4j components have been upgraded and an intermittent issue may be seen in some environments where the jaws.log may not be constantly written to everyday, or the logging that is there is limited.
AAI 6.5.4 and 6.5.4-1
1. Please make a backup copy of the log4j2.yml file in the <Install Dir>/jboss/standalone/jboss/configuration directory
2. Stop the AAI service
3. Download the attached log4j2.yml and replace the existing file with this new file
4. Start the AAI service and you should see more consistent logging
Note that this will be fixed in a future release of AAI without this workaround..