MSMTC large volume of STDERR output

Document ID : KB000047034
Last Modified Date : 14/02/2018
Show Technical Document Details

Question:  

Recently the MSMTC task started to produce large volumes of output in the STDERR DD. Everything is running fine and there are no error messages, but why the increased volume written to the STDERR DD? In the STDERR output we see the word FINE: repeatedly.

For example: 

FINE: Expanded ${catalina.base}/lib to /u/msmserv/csm60/msmruntime/tomcat
Sep 23, 2016 1:21:06 PM org.apache.catalina.startup.Bootstrap createClass
FINE: Expanded ${catalina.base}/lib/*.jar to /u/msmserv/csm60/msmruntime/
Sep 23, 2016 1:21:06 PM org.apache.catalina.startup.Bootstrap createClass
FINE: Expanded ${catalina.home}/lib to /u/msmserv/csm60/msmruntime/tomcat

Answer:

Full debug of Tomcat log was in effect. This should not be lft on in production and is the reason for the increased volumes of output to be written to the STDERR DD.

To turn off full debug of Tomcat log

1. Stop the MSMTC Tomcat

2. Update the SAMPLIB(MSMLIB) and comment the following line: 

#TOMCAT_LOGLEVEL="-debug" 

3. Start the MSMTC tomcat and you will no longer see the "FINE" logging messages written to STDERR.

Additional Information: 

CA Chorus Software Manager - 6.0, Rerun Failed Tasks with Debug Logging 
https://docops.ca.com/ca-chorus-software-manager/6-0-1/en/using/general-best-practices/rerun-failed-tasks-with-debug-logging