Servoy 7.x.x Documentation
Child pages
  • Server Log Settings

Versions Compared

Old Version 8

changes.mady.by.user Paul Bakker

Saved on

compared with

New Version Current

changes.mady.by.user Edit Mera

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The logging mechanism is highly configurable and enables control over:

  • the level of logging per area
  • the format of the log file
  • log file rollover/location/size settings

All log settings are stored in servoy.properties located in the <servoy>/application_server directory. The specific log properties are properties prefixed with 'log4j'.

...

Changing the log level

...

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.

Changing the Log Level

There are 6 levels of logging (In order of severity):

...

The first entry sets the log level for the internal Servoy Java class used for all logging done by Servoy.
The second entry sets the 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 log level and specifies the output channels for the log.

To change the the log level for Servoy, replace 'WARN' in the 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.

...

log

...

data

...

.

Servoy registers the following loggers:

  • com.servoy.j2db.util.Debug
  • com.servoy.j2db.persistence.Server
  • com.servoy.j2db.dataprocessing.ClientManager
  • com.servoy.j2db.terracotta.TerracottaStatusMonitor
  • com.servoy.j2db.persistence.XMLExporter
  • com.servoy.j2db.persistence.XMLImportHandlerVersions1to10
  • com.servoy.j2db.persistence.XMLInMemoryImportHandlerVersions11AndHigher
  • com.servoy.j2db.server.WebServer
  • com.servoy.j2db.persistence.datasource.TransactionConnection
  • com.servoy.extensions.plugins.rest_ws.RestWSPlugin (when plugin is available).

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
titleSet the loglevel to the most finegrained level for the ClientManager class
log4j.logger.com.servoy.j2db.dataprocessing.ClientManager=TRACE
Warning
title

Setting the 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 disk space is available.

Note
titleMore information on Log4J

For more information on log4j, visit http://logging.apache.org/log4j/ or visit the Frequently Asked Technical Questions section