TME 4.x logging…Support needs to know

When a problem occurs in any application the best place to start looking for answers is in the log files. Why would we be any different, the best way Nstein can help you resolve critical errors is by reading and analyzing the log files. In order for us, to help we need different levels of information.

TME has different levels of logging. What I would like to discuss is the most common information in the logs. The rest you can peruse at your leisure. (I know- find the time between Dan Brown’s work and TME.) For a more in depth look, please go to  TME Logging in the documentation section.

When you start the TME the two log files you should see are tme.log and tme.wrapper.log. Both are found in the “log” directory of your TME installation. You will find the messages below for different events.

Logging Levels

1) INFO - Runtime Events

2) WARN - Runtime events that are not desirable or unexpected, but not necessarily an error

3) ERROR -  Runtime errors or unexpected conditions

4) FATAL - Severe errors that cause premature termination

/!\ The following two should only be used when Nstein requests it. This slows down the TME considerably.

5) DEBUG - This gives detailed information

6) TRACE - More detailed information

In order to change the logging levels the file that needs to be edited is the log4j.properties located in the “etc” directory of your TME installation.
Appender Section - is used for file creation
Logger Section - used for logging levels

For more information about this file (There goes reading Dan Brown’s new novel of the month) you can go to Apache site