Understanding The Logs
The Effect of the Log Level Parameter
The initialization parameter
com.atomikos.icatch.console_log_level selects the level of details you will see in the log files. There are three possible values: WARN, INFO or DEBUG.
WARN
This is the default level, and will only show
serious warnings and/or errors. Use this level under normal production operation, since it offers the lowest overhead.
INFO
This log level will show all of the WARN information, plus additional
API-level interactions. This means that you will get an entry describing each interaction that crosses API boundaries, like XA calls, JTA calls and so on. This level will not show internal implementation details. Use this level if you want to diagnose interactions with third-party products.
DEBUG
This log level will show all of INFO plus additional
Atomikos-specific internal implementation details. Use this level only to debug or when asked by Atomikos support.
Annotated Examples
WARN Example
TODO
INFO Example
TODO
DEBUG Example
TODO
Log4J Integration
Note: this feature does not work for release 3.2.x or earlier...
You can configure logging to forward log messages to your own Log4J configuration. To do so, add the file
slf4j-log4j12-1.4.3.jar (located in the folder
included/slf4j of the installation folder) to your classpath. Then configure Log4J in a way similar to the example shown below.
log4j.appender.A1=org.apache.log4j.ConsoleAppender
log4j.appender.A1.layout=org.apache.log4j.PatternLayout
#configure a logger named 'atomikos' to capture the Atomikos log comments in log4j
log4j.logger.atomikos=INFO, A1
|
Make sure that the file called slf4j-nop-1.4.3.jar is no longer in the classpath, or things won't work as you expect.
|
Commons Logging Integration
Note: this feature does not work for release 3.2.x or earlier...
You can configure logging to forward to Jakarta commons logging. To do so, add the file
slf4j-jcl-1.4.3.jar (located in the folder
included/slf4j of the installation folder) to your classpath. Configure the commons logging facility with a logger called
atomikos.
|
Make sure that the file called slf4j-nop-1.4.3.jar is no longer in the classpath, or things won't work as you expect.
|
JDK 1.4 Logging Integration
Note: this feature does not work for release 3.2.x or earlier...
If desired, you can configure the logging to go into your own JDK log configuration. To do so, add the file
slf4j-jdk14-1.4.3.jar (located in the folder
included/slf4j of the installation folder) to your classpath. Configure the JDK logging facility with a logger called
atomikos.
|
Make sure that the file called slf4j-nop-1.4.3.jar is no longer in the classpath, or things won't work as you expect.
|
--
GuyPardon - 25 Jul 2007
