Log4j2 Configuration


The default Log4j2 configuration writes log output to 3 files:

Log fileDescription
app.log The main application log with information about the startup/shutdown process and with information about errors.
transactions.logThe transactions log containing 3-D Secure protocol messages, except preparation messages, exchanged with the Directory Server and the ACS.
preq-pres.logThe preparation request/response log containing the 3-D Secure protocol preparation messages exchanged with the Directory Server.

The log output is formatted according to a conversion pattern defined using a PatternLayout (file name: log4j2-prod.xml):

In addition to this, there are two more log4j2 configurations you can use. You can configure these using the logging.config property in the application properties.

Log output using a JSONLayout in the console (file name: log4j2-console-json.xml):

Log output in the console regularly (file name: log4j2-console.xml):

Mapped Diagnostic Context (MDC)

The 3DS Server application uses Mapped Diagnostic Context (MDC) to expose additional information available for log output.

Exposed info is the 3DS Server Transaction ID.

You can use information exposed via MDC in your log output by using the following conversion pattern:

For more details about conversion patterns please refer to the Log4j PatternLayout documentation.

Use your own configuration

Although not recommended, you can use your own Log4j configuration.

To do so, you have to override the logging.config property in 3DS Server Configuration Properties which specifies the location of the log4j configuration.