Growth of mdoaggregatorscript.out and AXA transformer nohup.out files

Document ID : KB000115226
Last Modified Date : 18/09/2018
Show Technical Document Details
Issue:
When using AXA 17.3, you may encounter issues with disk space, certain logs can grow very large.

In particular, the $CA_EMM_HOME/logs/mdoaggregatorscript.out file and $CA_EMM_HOME/java/axa-transformer/lib/nohup.out file can take up many GB, even hundreds of GB of space.
Environment:
AXA 17.3
Cause:
The logs are created from redirected stdout from the processes. There is no log4j configuration for the logs so they can grow uncontrolled.
Resolution:

The scripts that start these processes can be reconfigured to send the stdout to /dev/null. The additions to the default configuration are highlighted in bold:

  • $CA_EMM_HOME/java/mdo-aggregator/bin/ startAgg.sh

 

nohup ./Aggregator >> $CA_EMM_HOME/logs/mdoaggregatorscript.out > /dev/null 2>&1 &

 
 

  • $CA_EMM_HOME/java/axa-transformer/bin/ axa-transformer.sh

 

nohup "$javaExe" -XX:+HeapDumpOnOutOfMemoryError -Xms1024m -Xmx2048m -XX:NewRatio=2 -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -Djava.awt.headless=true  -Dservice=CA_AXA_TRANSFORMER -Djava.library.path=../lib -jar $jar_name -classpath "$CLASSPATH"  > /dev/null 2>&1 &


These configuration changes will be added to the product in a future release