LogLog.error just prints on the screen. The fact that there is no
hook to an ErrorHandler It looks like an omission to me. Cheers, Ceki
At 17:27 18.03.2002 +, you wrote:
> > Use ErrorHandler.
> > It's trivial to implement.
>
>Thanks for the suggestion - SocketAppender seems to call LogLog.er
I received an error:
java.lang.NoClassDefFoundError:
org/apache/log4j/or/jms/MessageRenderer
Is there a reason why this class is not in the
log4j-1.2beta4.jar file?
The class file (MessageRenderer.class) is in the
jakarta-log4j-1.2beta4\dist\classes\org\apache\log4j\or\jms
directory
and
the
Everyone,
All output from my test package only goes to the TestLogS.log file. I
really want logging statements from SimpleThread to go to TestLogS.log and
log statements in JimSimpleThread to go to TestLogW.log. Instead of all
statements going to TestLogS.log.
I search the history and this is
Ranjini,
Ceki has told me that that "must be running" bug has been fixed in 1.2 and
the code after 7/25/01 has changes for it. That bug has generated a tremendous
amount of traffic on the list, so if Ceki says it's fixed I believe him.
Sara,
As far as I can tell (I just looked at the cod
> Use ErrorHandler.
> It's trivial to implement.
Thanks for the suggestion - SocketAppender seems to call LogLog.error. Will this
hook into the ErrorHandler redirection, or will I need to modify the standard
SocketAppender.
TIA
- Rob
SoftSell Business Systems, Ltd.
' testing solutions for a
Try
log4j.additivity.com.myname.cog.y.z=false
- Original Message -
>I am facing another problem with Log4j. I am geting duplicate entries
in
> my log appender (in this case the console).
> Basically I defined two appenders for two categories in order to get two
> different formats of
Use ErrorHandler.
It's trivial to implement.
- Original Message -
From: "Rob Walker" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, March 18, 2002 10:16 AM
Subject: Not sure if this has been change
> Under 1.3.1, if a SocketAppender can't reach connect to it's destination i
Under 1.3.1, if a SocketAppender can't reach connect to it's destination it dumps
a pretty ugly stack trace with the "can't connect" message. Short of changing the
code, there's no easy way to suppress this output for what can be quite a
common occurrence.
Anyone enhanced/changed this area?
- R
Kevin,
The DailyRollingFileAppender in log4j1.1.3, would roll over the file at
the designated time, only if someone was using the application at the time.
For example, I had set mine to change at midnight and found that I had to be
using the application at midnight for it to work. Do you know if
Kevin-
I have not upgraded to log4j 1.2 yet, but do you know if the
DailyRollingFileAppender (regular) that was fixed for log4j 1.2 includes a
method to set the maximum number of log files to be kept? That is my
primary reason for using the DailyRollingFileAppenderExt (currently with
log4j 1.1.3
It is my understanding that the DailyRollingFileAppender (regular) is fixed for log4j
1.2. So the Extension version is only needed if you are using log4j 1.1.3
Kevin
Sara Prigge wrote:
> Hi Rob-
>
> Attached please find the DailyRollingFileAppenderExt.JAR file. Extract this
> into your log4j.
In early January '02 there was a discussion
(http://marc.theaimsgroup.com/?t=10101007052&r=1&w=2) between Ceki and
others about extending DOMConfigurator and/or PropertyConfigurator to use
the log4j.configuration property. This extension would allow for
configureAndWatch() type functional
12 matches
Mail list logo
