JRun Administrator's Guide
Logging

Default logging configuration

When using the default logging configuration and a logging event occurs in your application, JRun transfers the event to an in-memory queue and returns control immediately. A background thread then reads events from the queue and forwards each event to the appropriate destination.

The following figure shows the default configuration of the logging mechanism:

The following processes occur in this default configuration:

1. A threaded logger acts as the event listener. When a log event occurs, a message describing the event is written to the threaded logger's queue.
2. The threaded logger's background thread reads the event from the queue and sends it to the file writer.
3. The file writer writes the event to a file named jrun_root/logs/jrun_server-event.log.
4. You can use the JMC to control maximum log size and the number of rotation files. When the log file reaches the specified maximum size, JRun stops writing to the current log file, renames it by appending a sequential number, and creates a new log file. All new events are written to the new log file.

You control the logging configuration through the JMC and can further customize it in the jrun.xml file, if necessary. For more information, see "LoggerService" and the JMC online Help.

RSS feed | Send me an e-mail when comments are added to this page | Comment Report

Current page: http://livedocs.adobe.com/jrun/4/JRun_Administrators_Guide/logging3.htm

Add Comment