Page History
...
- com.servoy.j2db.util.Debug
- persistence.Server
- ClientManager
- com.servoy.j2db.persistence.XMLExporter
- com.servoy.j2db.persistence.XMLImportHandlerVersions1to10
- com.servoy.j2db.persistence.XMLInMemoryImportHandlerVersions11AndHigher
- com.servoy.j2db.dataprocessing.editedRecords
- WebServer
- datasource.TransactionConnection
- com.servoy.j2db.server.ngclient.MessageLoggerperformance.timing.methods
- com.servoy.performance.timing.sql
- ResourceProvider
- loggers related to jsunit tests:
- com.servoy.automation.jsunit.runner.ImportClient
- com.servoy.automation.jsunit.SolutionJSTestSuite
- com.servoy.automation.jsunit.mobile.ServoyMobileJSUnitTestRunner
- com.servoy.eclipse.jsunit.runner.JSUnitToJavaRunner
- com.servoy.mobile.test.server.service.TestSuiteController
- sablo (part of NGClient impl) related loggers :
- org.sablo.BrowserConsole
- org.sablo.eventthread.Event
- org.sablo.eventthread.EventDispatcher
- org.sablo.services.server.FormServiceHandler
- sablo property type related loggers (start with org.sablo.specification.property):
- org.sablo.specification.property.types.TypesRegistry
- org.sablo.specification.property.types.DoublePropertyType
- org.sablo.specification.property.types.EnabledSabloValue
- org.sablo.specification.property.types.FloatPropertyType
- org.sablo.specification.property.types.IntPropertyType
- org.sablo.specification.property.types.LongPropertyType
- org.sablo.specification.property.CustomJSONPropertyType
- org.sablo.specification.property.CustomPropertyTypeResolver
- org.sablo.specification.property.BrowserConverterContext
- loggers related to sablo packages and specification (start with org.sablo.specification):
- org.sablo.specification.Package
- org.sablo.specification.WebObjectSpecification
- org.sablo.specification.WebLayoutSpecification
- org.sablo.specification.WebComponentSpecProvider
- org.sablo.specification.WebServiceSpecProvider
- org.sablo.specification.WebSpecReader
- loggers related to classes close to web socket communication (start with org.sablo.websocket):
- org.sablo.websocket.impl.ClientService
- org.sablo.websocket.utils.JSONUtils
- org.sablo.websocket.utils.PropertyUtils
- org.sablo.websocket.BaseWebsocketSession
- org.sablo.websocket.BaseWindow
- org.sablo.websocket.WebsocketEndpoint
- org.sablo.websocket.WebsocketSessionManager
- org.sablo.BaseWebObject
- org.sablo.CustomObjectContext
- org.sablo.IndexPageEnhancer
- ngclient related loggers:
- com.servoy.less.Compiler
- ngclient property type related loggers:
- com.servoy.j2db.server.ngclient.property.types.FormatPropertyType
- com.servoy.j2db.server.ngclient.property.ComponentTypeSabloValue
- com.servoy.j2db.server.ngclient.startup.resourceprovider.ResourceProvider
- com.servoy.j2db.server.ngclient.MessageLogger
- com.servoy.j2db.server.ngclient.api
- com.servoy.extensions.plugins.rest_ws.RestWSPlugin
- com.servoy.j2db.server.main.Activator
- com.servoy.j2db.server.headlessclient.ServoyModificationWatcher
- com.servoy.j2db.util.ImageLoader
- com.servoy.PersistIndexCache
- plugin.oauth
The logging level can be set independently of for subsets of all these loggers, by adding extra 'log4j.logger' entries in the servoy.properties / log4j.xml file (depending on what version of Servoy you are using); for example:
...
Warning | ||
---|---|---|
| ||
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 for the log file(s). |
Logging Pattern
The pattern in the log4j.xml defines what information is logged. Log4j supports a number of lookups, Servoy has added servoy-lookup (starting from release 2021.06) that can be used to print Servoy-specific data in the logfile.
The lookup is called servoy and can be used like in this example. Note that the double dollar-sign is needed to ensure that the value is looked up for each message, otherwise Log4j may cache the value.
Code Block |
---|
<PatternLayout
pattern="%d %p [%t] %c - %m [$${servoy:clientid:-(NO CLIENT)} $${servoy:solution:-(NO SOLUTION)}]%n" /> |
The supported lookup keys are:
- clientid
- solution
- username
- useruuid
- clienttype
- hostname
- hostaddress
- sessionkey (ng client only)
Note | ||
---|---|---|
| ||
For more information on log4j, visit the Log4j site (Frequently Asked Log4j Questions section can help with some questions). |
...