...
Some jobs of JobScheduler use log4j for logging and it could be necessary to configure these jobs with its own log4j configuration. To do this there are in general different possibilities described below.Currently it is not allowed to use log4j configuration in xml format.
Starting with Release 1.13.3 the JobScheduler Master and Agent, YADE as well as JOC Cockpit uses log4j 2 with xml configuration files.
Configuration by class path
To do this the configuration file has to be located in the class path defined in your factory.ini. To enable log4j to find it automatically it has to be stored with the name log4j.properties.
| Note |
|---|
Starting with Release 1.13.3 using log4j2 the name of the configuration file has to be Also, the java option was renamed by log4j2 to be |
...
|
As some of the libraries used by JobScheduler come with their own log4.properties file, this option is not recommended as it is not determined which of the property files would be selected.
...
| Code Block | ||
|---|---|---|
| ||
<config ... java_options="-Dlog4j.configuration=file:/${SCHEDULER_DATA}/config/my-log4j.properties" />
|
| Note |
|---|
Starting with Release 1.13.3 the java option has to look like this: |
Configuration as a specific setting for a job
...
| Code Block | ||
|---|---|---|
| ||
<job ... java_options="-Dlog4j.configuration=file:/${SCHEDULER_DATA}/config/my-log4j.properties" />
|
| Note |
|---|
Starting with Release 1.13.3 the java option has to look like this: |