Page History

Since version v1.5.3100-beta of the JobScheduler Engine it is possible to configure a logging API of your choice to handle log messages from JobScheduler (assumed the logging API is supported by slf4j). Using this feature you have a wide range of possibilities to handle your logs, e.g. filtering, mailing, eventing etc.

Please look at How_to_configure_JobScheduler_logging for more information.

If you find in the output of JobScheduler the lines

 log4j:WARN No appenders could be found for logger (com.sos.scheduler.engine.kernel.plugin.PluginConfiguration).
 log4j:WARN Please initialize the log4j system properly.
 log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.

after you have started or stopped the JobScheduler then the JobScheduler logging uses log4j but log4j did not find a configuration file.

Starting from release 1.5.3253 JobScheduler is shipped with an active log4j logging as a slf4j-log4j12-x.jar is added to the java class path.

 [java]
 class_path = ${SCHEDULER_HOME}/lib/*.jar;${SCHEDULER_HOME}/lib/hibernate/*.jar;${SCHEDULER_HOME}/lib/jetty_ext/*.jar;${SCHEDULER_HOME}/lib/log/log4j/*.jar

but without a log4j configuration file.

In this case please create a default log4j configuration file ./lib/log4j.properties with the following content:

 log4j.rootLogger=info, stdout
 log4j.appender.stdout=org.apache.log4j.ConsoleAppender
 log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
 log4j.appender.stdout.layout.ConversionPattern=%5p [%t] (%F:%L) - %m%n

and edit the ./config/factory.ini file with

 [java]
 class_path = ${SCHEDULER_HOME}/lib/*.jar;${SCHEDULER_HOME}/lib/hibernate/*.jar;${SCHEDULER_HOME}/lib/jetty_ext/*.jar;${SCHEDULER_HOME}/lib/log/log4j/*.jar
options    = -Dlog4j.configuration="file:///${SCHEDULER_HOME}/lib/log4j.properties"

so that log4j finds the configuration file.