Release History > PTV xServer 1.34 > Migration Guide Logging

Migration Guide Logging

PTV xServers before 1.34 did use log4j1-Framework, which has reached its end of life. Starting with PTV xServers 1.34 log4j2-Framework is used as logging framework. The logging configuration is still based on properties files and still contains different optional settings which can be activated.

As the configuration syntax differs between these framework versions, some configuration files had to be adapted to a valid log4j2 configuration:

server-logging.properties
module-logging.properties
wms.properties (the included logging configuration part, only)

If you have run a preceding version of PTV xServer with adaptions in one of these files please apply them to the new configuration. Also please note, that the configuration of engine logs is not affected by this change, which is part of the logging.properties file.

Further changes concerning logging configuration:

The placeholders that can be applied for the default log directory, the service name and the instance ID use system properties, now (cf. also Logging Configuration).
The configuration for startup tasks was moved from logging.properties to server-logging.properties.
By default all log4j2 loggers log asynchronously, activated by system property log4j2.contextSelector=org.apache.logging.log4j.core.async.AsyncLoggerContextSelector in the wrapper.conf.
Logfile appenders for server-side scripting write to separate files for each service and are deactivated by default.