Log Files
Log files contain a trace of JMap Server activity. Depending on the selected logging level, a different quantity of events is written in the log files. By default, a new log file is created every day but this parameter can be adjusted. By default, log files are located in directory JMAP_HOME/logs. You may need to periodically check the volume of the log files and archive or delete old ones.
Log files can be viewed online and analyzed to determine the number of occurrences of different types of events. A special analysis tool can be used to analyze logins, to know which users connected to JMap Server, how many times, and when.
Log files parameters |
|
Log level |
The maximum level of the messages added to the log files. For example, if WARNING is selected, only messages with a level of WARNING, ERROR or FATAL will be written in the log files.The following log levels are available (listed in decreasing order) : All: Every event is written. Use only to solve a problem. Debug: Debug level events are written. Use only to solve a problem. All lower level events are also written. Info: Information level events are written. This includes user logins. All lower level events are also written. Warning: Warning (non serious) level events are written. All lower level events are also written. Error: Error (serious) level events are written. All lower level events are also written. Fatal: Only fatal error (very serious) events are written. Off: Nothing is written. |
Log file directory |
Directory where to create the log files. Default is under JMAP_HOME/logs. Make sure there is sufficient disk space to hold log files. |
File age limit |
The file age limit determines how often new log files are created. The current log file is always called jmap_log. When a new file is created, the current log is renamed to include the date (e.g. jmap_log_2006_05_23.log). |
Send messages to console |
Determines if events will also be written in JMap Server screen console. This is useful in tests or development but should be turned off in production. Moreover, when JMap Server has no output console (started as a background process or as a service on Windows), this option is useless and consumes computer resources for nothing. |
Viewing log files
Log files (and error files) can be viewed directly in JMap Admin. Select only one file from the list and press View Log. The content of the file is displayed. Note that error files are also listed along with log files. The error files contain only error messages that can sometimes complement the log files to help solve a problem.
Analyzing log files
Log files can be analyzed in order to provide a summary of the activity of JMap Server. For instance, they can inform you of the number server shutdowns, authentication failures, etc. You can analyze many log files at the same time by selecting them in the list.
Analyzing logins
A special analyzing tool can be used to provide information about user logins. This informs you about which users have used JMap, how many times they logged in and when each user last used it.