Is this problem reproducible?
By the way, in 1.1.3. line 753 in Category.java is javadoc not an
executable java statement. So the following line
at org.apache.log4j.Category.isDebugEnabled(Category.java:753)
is somewhat suspicious. Can you check what line 753 corresponds to in
your copy of
We have been using log4j (v113) successfully for some time now with
Weblogic 6.1and J2SE 1.3.1_02 on Sun Solaris.
We have just started experiencing what appears to be a log4j problem (!!)
in one of our environments.
At startup time log4j is configured successfully , but when a call is made
to isDe
