[TRAFODION-2596] Improve the log4j and log4cxx infrastructure in Trafodion Removed setting the root logger to be the appender logger in most of the configuration files. This would allow T2 driver applications to have control over the logging in their layer to its preferred way. But, the logging in SQL engine layer will be controlled by the Trafodion engine itself.
Changed the code so that the logging location and the file name is picked up from the config file.
Java part of the code base TM trafodion.dtm.log log4j.dtm.config SQL trafodion.sql.java.log log4j.sql.config
By default, the log level is set to INFO for most of the cases. When a message dominates the log file and if doesn't add value in the current level, it will be changed to the higher level in the hierarchy. This should help to improve the usefulness of the log file at the default INFO level.
The existence of an environment variable TRAF_MULTIPLE_SQL_LOG_FILE will revert back to the old way of logging into multiple files. Then, the configuration file log4cxx.trafodion.masterexe.config will be used.
Currently, RollingFileAppender appender is used for both modes. Different config files are used to change this appender when the need arises.
log4cxx.trafodion.udr.config and log4cxx.trafodion.lob.config are removed. log4j.hdfs.config used as the config file for SQL is renamed to log4j.sql.config
Foundation components logging will be revamped later.