Logging

In the standard system, the Scheduler directs any log output to the following file (with no output on stdout):

logs/ColdScheduler.log

You can specify which log messages are to be written in the file:

conf/LogConfig.xml

The following log levels exist: ERROR, INFO, DEBUG, and TRACE

Loggers, which are recommended as standard, are activated by default with level “INFO”:

<logger name="com.tsystems.coldscheduler.comm" level="INFO" />
<logger name="com.tsystems.coldscheduler.database" level="INFO" />
<logger name="com.tsystems" level="INFO" />
<logger name="com.tsystems.coldscheduler.database.DbSql" level="INFO" />

The following loggers are appropriate for troubleshooting and error analysis.

Database - selects:

<logger name="com.tsystems.coldscheduler.scheduler.JobsDao" level="DEBUG" />

Example log output:

13:56:54.685 [Scheduler] DEBUG c.t.c.s.JobsDao - select id, spoolfile, generation, attempts, state, type, status, stop, data from cold_steuer where data <= SYSDATE and status=? and serverid=? and stop!=1; [Waiting, 1]

Scheduler:

<logger name="com.tsystems.coldscheduler.scheduler.Scheduler" level="DEBUG" />

Example log output:

13:54:18.034 [Scheduler] INFO  c.t.c.s.Scheduler - Fetching job list...

Jobs:

<logger name="com.tsystems.coldscheduler.scheduler.JobRunner" level="DEBUG" />

Example log output:

11:17:15.913 [JobRunner-0] INFO  c.t.c.s.JobRunner - Job (8662)[DemoSpool/8364] Initialize(10)  started...
11:17:17.015 [JobRunner-0] INFO  c.t.c.s.JobRunner - Job (8662)[DemoSpool/8364] Initialize(10)  finished with status 9

Monitoring interface:

<logger name="com.tsystems.coldscheduler.monitoring" level="DEBUG" />

Aktion.ini reading routine:

<logger name="com.tsystems.coldscheduler.action" level="DEBUG" />

Global debugging of all components:

<logger name="com.tsystems" level="DEBUG" />