DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=36041>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=36041


[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Include class loader        |[logging] Include class
                   |information when            |loader information when
                   |LogFactoryImpl throws       |LogFactoryImpl throws
                   |LogConfigurationException.  |LogConfigurationException.




------- Additional Comments From [EMAIL PROTECTED]  2005-08-08 08:12 -------
The current trunk version of commons-logging includes the ability to generate a
great deal of diagnostic information about what it's doing internally.  If
commons-logging is behaving in an unexpected manner, you can now set system
property org.apache.commons.logging.diagnostics.dest to the value STDOUT, STDERR
or a filename and you'll get detailed diagnostics.

Specifically, if an incompatible Log problem occurs, you would get a diagnostic
message like the following:

"Class org.apache.commons.logging.impl.Log4J12Logger was found in classloader  
[EMAIL PROTECTED] It is bound to a Log interface which is not     
                  the one loaded from classloader
[EMAIL PROTECTED]"

Prior to this message there would be other diagnostic info showing how
commons-logging came to be using [EMAIL PROTECTED] and
[EMAIL PROTECTED]

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to