Hi,
Looking at the source of the LoggingEvent class I see that the
getLocationInformation() method creates a new LocationInfo object using
a new Throwable, and not the throwable that might be referenced by the
LoggingEvent's member throwableInfo. Considering that the LocationInfo
class searches
Hi, Andreas
New a Throwable() will create the full stack trace information in the
throwable instance. The log4j parse the stack trace and get the
LocationInformation. But it's of no use to the class in the same package
with LoocationInfo(or LogEvent)
It's heavy burden to create lots of
At 09:16 AM 11/4/2003 +0200, you wrote:
Hi,
Looking at the source of the LoggingEvent class I see that the
getLocationInformation() method creates a new LocationInfo object using
a new Throwable, and not the throwable that might be referenced by the
LoggingEvent's member throwableInfo.
Hi Everyone
I'm getting the following error upon switching from Weblogic 6.1 sp2 to Weblogic 7.0
(with log4j1.2.3). I'm not sure if that can cause the issue, but it's the only change
from a configuration that wa working perfectly fine...
log4j:ERROR Could not close [EMAIL PROTECTED]
Using a single utility class to log messages is exactly against the log4j
paradigm. Log4J allows different classes to have their own individually
configured logger instances according to your wishes as specified in the
*.properties or *.xml file. The utility class would itself be using only a
I am using the Log Tag Library 1.0 from Jakarta Project.
In the Installation document, it suggest that in order to initialize
Log4j automatically, the log4j.properties file will have to be placed in
/WEB-INF/classes.
How could I put the log4j.properties file in /WEB-INF/classes/config