ode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tammo van Lessen (JIRA)" <j...@apache.org>
Subject [jira] Created: (ODE-722) Configure logging system properly
Date Wed, 02 Dec 2009 10:54:21 GMT
Configure logging system properly

                 Key: ODE-722
                 URL: https://issues.apache.org/jira/browse/ODE-722
             Project: ODE
          Issue Type: Improvement
            Reporter: Tammo van Lessen
            Assignee: Tammo van Lessen
            Priority: Minor
             Fix For: 1.3.4, 2.0

There are two issues with the current log configuration:

a) The currently used log pattern makes use of %C{1} (classname) and %L (line numbers), which
are, according to log4j docs, extremely slow. In addition, the information we get using these
setting are quite useless due to b).

b) Instead of Log4J, commons logging finds the GeronimoLogFactory, which creates a wrapper
for each log call. This result is that we lose the class and line number information of the
originating log call and get instead something like GeronimoLog.debug(66).

Proposed fix: 
a) ship ODE with a different default log pattern, including timestamp and log category (instead
of classname and line numbers).
b) have an alternative log pattern for better debug output (classname, linenumbers, threadname).
c) set LogFactory to log4j.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message