Logging in Weave is done using the a third party library. Prior to Weave 2.6.7 Log4j 1.2 was used, from . From 2.6.7 onwards Logback is used. It is beyond the scope of this document to explain how the logging infrastructure works with Log4j and Logback so the reader is encouraged to visit the Log4j or Logback websites to find out more information about the inner workings of these libraries.
...
| Code Block |
|---|
00:06:45,405 DEBUG [OSGi Console] com.cohga.search.indexer.internal.Activator "Stopping Weave Index ..." |
Item | Value | Description |
|---|---|---|
TIME | 00:06:45,405 | States the time the message was logged to the file. Format is HOURS:MINUTES:SECONDS,MILLISECONDS |
LOGGING_LEVEL | DEBUG | The Level of the message logged. Possible values are DEBUG, WARN, INFO or ERROR |
THREAD | [OSGi Console] | The thread that the message was logged in (See below for more information about reading logs). |
MESSAGE_ORIGIN | com.cohga.search.indexer.internal.Activator | The class that the message was logged against. e.g. The class Activator in the package com.cohga.search.indexer.internal |
MESSAGE | "Stopping Weave Index ..." | The message that is being set to the log. Typically this is in human readable form, however sometimes the messages may not be that intuitive to the user. |
The main items that change, and that should be noted are the Thread, Message Origin and the Message. These three items define when and where the message was logged from. The Thread component can cause some confusion to many first time readers if they have not familiar with multithreaded applications. A key example is that the same message may be logged three times in succession. This happens due the the WebService, that Weave runs under, which is handling requests from multiple different locations at the same time. Each thread is being executed concurrently and working in isolation within the Weave application. An example of what you would see in the log file for this is:
...