Activating debug mode
ForecastingShell Server
Set the system environment variable LOG4J_DEBUG to true for the service account in which the forecasting shell is running.
Operator Client
See also ClientConfig XML File for Operator Client and Forecasting Shell Servers - 2018.02 - 2021.01.
- Temporarily rename the clientConfig file for an OC to prevent it is overwritten with the uploaded file.
Set logging / debugEnabled to true in the clientConfig.xml.
Code Block language xml <?xml version="1.0" encoding="UTF-8"?> <clientConfiguration xmlns="http://www.wldelft.nl/fews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.wldelft.nl/fews http://fews.wldelft.nl/schemas/version1.0/clientConfig.xsd"> <clientType>Stand alone</clientType> <logging> <debugEnabled>true</debugEnabled> </logging> </clientConfiguration>
- Ignore the error message about the clientConfig xml not being available in the central database.
Stand alone
Activate the "W debug logging enabled" option in the F12 menu.
Configuring the log.txt file of FEWS can be done using the Log4jConfig.xml in the root of the FEWS directory.
By default the log file is configured as follows:
<appender name="defaultLogFile" class="org.apache.log4j.FileAppender">
<param name="File" value="$
...
"/>
<param name="MaxFileSize" value="20MB"/>
<!-- Keep 5 backup file -->
<param name="MaxBackupIndex" value="5"/>
<param name="Append" value="true"/>
<layout class="org.apache.log4j.PatternLayout">
<!-- [Date] Priority - category - Message\n -->
<param name="ConversionPattern" value="[%d] %p - %C
{1}
.%M - %m%n"/>
</layout>
</appender>