Summary: | NullPointerException in org.apache.log4j.NDC.get | ||
---|---|---|---|
Product: | Log4j - Now in Jira | Reporter: | Curt Arnold <carnold> |
Component: | Other | Assignee: | log4j-dev <log4j-dev> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | christenseningrid |
Priority: | P2 | ||
Version: | 1.2 | ||
Target Milestone: | --- | ||
Hardware: | Other | ||
OS: | other |
Description
Curt Arnold
2006-08-02 04:17:08 UTC
Patch committed in rev 427881. Waiting for feedback before marking as closed. Hello, This problem does also occur in the MDC. I got the NullPointerException in NDC.get() as mentioned here and now in the MDC.get(). I think both are related to each other, so that's why I added this comment here. The exceptions are raised in my case, when I trigger a reload of a Tomcat context which uses Log4j as the logging system. Tomcat reloads the context and then: - before Log4j 1.2.14: NullPointerException at NDC.get (as mentioned here) - now: NullPointerException at MDC.get(). There propably the tlm==null. Can this be fixed too with a "not-null-check" in the next release of Log4j as was done with NDC.get()? Thanks Reopening so Steven's comment gets noticed. |