Child pages
  • Configuring application specific logging with Log4j
Skip to end of metadata
Go to start of metadata

(Available in Geronimo 2.1.1 and later)

Geronimo uses log4j for logging and the base log4j configuration is in var/log/ If your application also uses log4j for logging you can configure logging in this file. However, this is not self-contained. Instead, you can configure log4j settings specific to your application in your application plugin.

Note that in any case, unless you use hidden-classes or inverse-classloading to load your own copy of log4j separate from the geronimo copy, log4j will not automatically read any files you may have included in your classpath.

If you are building your own application:

This example is taken from the apache directory plugin for geronimo, so the paths etc are adapted for that plugin.

  1. Include an ApplicationLog4jConfigurationGBean in your application plan, like this:
    You can also use a file in your classpath, for example, in WEB-INF/classes/META-INF. (If you prefer not to place this file under WEB-INF/classes/, the path of this file must be added to your classpath). But this will obstruct anyone trying to configure logging as the file will remain packed in your application somewhere hard to find.
  2. Configure application specific logging in your file. The gbean prevents you from overriding settings that apply to global logging, but you can configure appenders for specific loggers for your application. Here's the example for ApacheDS:

If you are building a plugin using maven and the car-maven-plugin:

  1. Include the configuration file in an appropriate location in your plugin, say META-INF/
  2. Unpack the file during plugin installation by including something like this in the pom.xml that generates geronimo-plugin.xml:

If you are deploying your app by some other means:

Copy the file by hand to the appropriate location such as var/my-app/ There is no need to include this file in your app.

  • No labels