...
The logging mechanism is highly configurable en and enables control over:
...
...
All log settings are stored in servoy.properties located in the <servoy>/application_server directory. The specific log properties are properties prefixed with 'log4j'.
Besides the log4j properties, administrators can also configure the servoy.client.report.max.valuelist.items property on the Servoy admin page, or directly in the servoy.properties file. This property is used to disable/enable the logging of messages that not all records can be loaded into the valuelist, i.e. when the valuelist contains more than 500 records. It is not recommended to set this property to false when running from the Servoy developer, otherwise the developers will not be aware of these warnings at all.
...
There are 6 levels of logging (In order of severity):
By default, the loglevel log level is set to WARN. This means that all WARN, ERROR and FATAL messages will be logged. In the servoy.properties file, there are three entries:
Code Block | ||
---|---|---|
| ||
log4j.logger.com.servoy.j2db.util.Debug=WARN log4j.logger.org.apache.wicket=WARN log4j.rootCategory=WARN, file, configservlet |
The first entry sets the loglevel log level for the internal Servoy Java class used for all logging done by Servoy.
The second entry sets the loglevel log level for the Java class used for all logging of the Wicket framework, used for the Servoy Web Client
The third entry sets the overall loglevel log level and specifies the output channels for the log.
To change the the overall loglevellog level for Servoy, replace 'WARN' in the third first entry with, for example 'TRACE' to get the most logging information. The overall log level could also be set, but this would generate a lot of log data.
Servoy registers the following loggers:
The logging level can be set independently for all these loggers, by adding extra 'log4j.logger' entries in the servoy.properties file, like:
Code Block | ||
---|---|---|
| ||
log4j.logger.com.servoy.j2db.dataprocessing.ClientManager=TRACE |
Warning | ||
---|---|---|
| ||
Setting the loglevel log level to DEBUG or TRACE will generate a lot of logging data. This is not recommended in a production environment, unless absolutely necessary. Make sure enough diskspace disk space is available. |
Note | ||
---|---|---|
| ||
For more information on log4j, visit http://logging.apache.org/log4j/ or visit the Frequently Asked Technical Questions section |