Log file tracking

The system writes many kinds of log files to its logs and other directories. These logs are mainly used by software developers to troubleshoot and not intended to be used by end users. However, experienced users can gain insight into processing activity by examining specific log files.

Tip   Log files contain a complex array of data that takes practice to interpret.

For example, detailed information about system events and how to manage and route them to various log files are located in System events.

The following topics describe the log files:

Event logs

Event logs contain selected events from the event subsystem. These are events related to message processing activity. You can review these logs to monitor processing activity. They are written to <install directory>\logs.

  • server_ events.log reports user-initiated configuration events for a machine.

The content of the default event logs can be filtered or extended. New event logs can be created using the event system configuration. For more information see System events.

System logs

System logs, used by software developers for troubleshooting, contain formatted, time-stamped information reported by various components of the application. Activator uses the Apache Jakarta Project's log4j framework to format and manage the logs, which are generated by each Java virtual machine during runtime. The log4j2.xml file in <Activator_install_directory>\Activator\conf\<hostname>\server can be edited to generate debug level events in log files.

For information about Apache logging services, see

See Troubleshoot with the log4j2 file for information about changing and using the file.

The system names the logs based on the names of the source JVM node. They are written to <Activator_install_directory>\Activator\logs. The logs are server.log reports processing activity of Activator.

System logs can report four levels of events. These are, in order of verbosity:

  • Error messages indicate a possibly serious error affecting service.
  • Warn messages typically have operational significance, but might not affect service.
  • Info messages provide general processing information useful for troubleshooting.
  • Debug messages typically have detailed information useful for troubleshooting. This level should be turned on only when necessary, as it can degrade system performance and uses large amounts of disk space.

The four logging levels are cumulative. Error messages are included at the warn level, both of which are included at the info level, and everything is logged at the debug level. The debug level also produces further details about processing.

System statistics logs

All logs file appended with stats.log are Java Management Extensions (JMX) monitoring and statistics logs. There can be many of these files, depending on how many processing nodes are active.

These logs are used by software developers for troubleshooting.

User interface logs

User Interface logs, used by software developers for troubleshooting, are created by the user interface. These logs are written to <Activator_install_directory>\Activator\logs\ui.

The names have the following format: server.log.000001. The trailing number (000001) identifies rolling logs. Once a log reaches a certain size, events write to another log (000002). This rolling occurs up to five times before events again start writing to the first log file.

HTTP server logs

HTTP server logs are written by the embedded HTTP server when a control node or service node is started with the -Ddebug startup option.

Class path logs

Class path log files, appended with classpath, contain information about all JARs in class paths.

Console logs

Log files appended with console contain standard output (stdout) and standard error (stderr) output streams from embedded third-party software.

Related Links