[jboss-jira] [JBoss JIRA] Updated: (JBAS-3316) outdated log4j.jar causes UndeclaredThrowableException

[Dimitris Andreadis (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-3316?page=all ]

Dimitris Andreadis updated JBAS-3316:
-------------------------------------

    Fix Version/s: JBossAS-4.0.6.CR1
                       (was: JBossAS-4.0.5.CR1)

Not likely to upgrade log4j for 4.0.5

> outdated log4j.jar causes UndeclaredThrowableException
> ------------------------------------------------------
>
>                 Key: JBAS-3316
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3316
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Logging
>    Affects Versions: JBossAS-4.0.4.GA
>         Environment: java version 1.5.0_06 macosx
>            Reporter: afm
>         Assigned To: Scott M Stark
>             Fix For: JBossAS-4.0.6.CR1
>
>
> The log(String callerFQCN, Priority level, Object message, Throwable t) method of org.apache.log4j.Logger
> in the log4j.jar distributed with JBoss throws a NullPointerException if called with t = null. This then
> causes an InvocationTargetException on line 288 of org/apache/commons/logging/impl/Log4jProxy.java,
> leading to an UndeclaredThrowableException on line 296. The problem is that very often the method is
> called with t = null, e.g. on line 235, in the debug method. This then causes some servlets not to work
> (Google finds a few instances of this).
> The cause is a rather outdated log4j.jar. Replacing log4j.jar by a more recent version seems to
> fix this problem

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira