Projects:Upgrade to Log4j2/QA
Contents |
Tests
To create the new Log Management screen, it was required to create a manual Datasource to fetch all Loggers from the log4j configuration. A test case is created to ensure it lists, orders and filters data properly. TODO add test case link when pushed.
Testing Build from UI
This project affects the build from UI feature in Module Management window. The following scenarios were tested to make sure it still works as expected:
https://docs.google.com/spreadsheets/d/1Yy0OxGVH0ooi-gFvfouHwZxVfEYdZEU121OmAD_skMc/edit?usp=sharing
Performance
One of the big improvements the Apache Foundation advertises about log4j 2 is that this implementation is garbage-free or low garbage. This behavior can be observed in a test performed to verify the cost of archiving big (1GB) log files.
Monitoring the JVM resources using VisualVM it can be noticed that a separate thread is created to do the rollover task and this is done in around 5-6 seconds independent of the number of files being rolled, which is an acceptable value.
Heap does not seem to be specially affected by the rollover and the CPU shows a peak only when processing and compressing the log file.
Code review
https://docs.google.com/spreadsheets/d/1FB7qFmhoiwr6NtkEScohS_X20bLxgoJLiG7krkePRsw/edit#gid=0