Child pages
  • Server Log Settings

Versions Compared

Key

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

...

By default, the 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  Starting with Servoy 8.4 all log settings are in a separate file: log4j.xml. Some entries we have there:

Code Block
titleLeglevel Log level settings in servoylog4j.propertiesxml
log4j.logger.com.servoy.j2db.util.Debug=WARN
log4j.logger.org.apache.wicket=WARN
log4j.rootCategory=WARN, file, configservlet

...

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.

Servoy registers the following loggers:

...

See an example of a log entry, the pattern is defined in PatternLayout:

Code Block
titleLog entry
2019-03-25 10:48:52,965 ERROR [Executor,uuid:3f0bccdb-0dec-42fd-8c06-81b67fad3bce] com.servoy.j2db.util.Debug - error getting data from global method valuelist 

It starts with date, log level (Error in this case), thread that logged this error, logger name then message. In this case, this message is logged under: com.servoy.j2db.util.Debug logger. So, in order to hide/show/customize this message you have to use that logger name in log4j.xml .

Servoy registers the following loggers:

  • com.servoy.j2db.util.Debug
  • 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
  • datasource.TransactionConnection
  • com.servoy.automation.jsunit.runner.ImportClient
  • com.servoy.automation.jsunit.SolutionJSTestSuite
  • com.servoy.j2db.persistence.datasource.TransactionConnection.server.ngclient.MessageLogger
  • ResourceProvider
  • com.servoy.less.Compiler
  • org.sablo.BrowserConsole
  • WebsocketSessionManager (and other different sablo classes)
  • 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 servoylog4j.properties xml file, like:

Code Block
titleSet the loglevel to the most finegrained level for the ClientManager class
log4j.logger.com.servoy.j2db.dataprocessing.ClientManager=TRACE

...