Log4j users/developers
I've now tried endless combinations of parameters to the different
rollingfile appenders (CompositeRollingAppender, DailyRollingFileAppender,
RollingFileAppender) in log4j and they all make the application hang after a
rollover-attempt.
The application has a lot of
Log4j users/developers
I've now tried endless combinations of parameters to the different
rollingfile appenders (CompositeRollingAppender,
DailyRollingFileAppender,
RollingFileAppender) in log4j and they all make the
application hang after a
rollover-attempt.
The application has a
http://www.tuxedo.org/~esr/faqs/smart-questions.html
At 10:57 27.09.2001 +0100, you wrote:
Log4j users/developers
I've now tried endless combinations of parameters to the different
rollingfile appenders (CompositeRollingAppender, DailyRollingFileAppender,
RollingFileAppender) in log4j and they
I get the gist of the original message here... but what is your
reply?
As I read it, Ceki's reply is basically saying, Please follow the
guidelines in this document - in other words, give us some more data to
work with, etc.
It's important that this gets fixed, but without more
Stephen,
Ceki pointed out that I was imprecise (and probably rude), and he was
totally right. I went out of my way (my apologies to the log4j development
team). I didn't mean that other people should refrain from using log4j, I
just pointed out that I personally will consider it in
Thanks for your *open* response
... and I, for one, will be looking forward to the resolution of this
issue...
regards, Stephen
-Original Message-
From: Thomas Tuft Muller [mailto:[EMAIL PROTECTED]]
Sent: Thursday, September 27, 2001 8:58 AM
To: LOG4J Users Mailing List
Subject:
snip
Will send the results to Jon Skeet who most kindly promised
to look into it.
Like Stephen, I'd like to say thanks for the open post :)
One thing though: I'll certainly look into any code you send me, but
would you mind if others did too? I'm far from an expert on Log4j and
the more
Hi
I have made a few mod's to the SocketAppender. You can now specify an additional
optional parameter
called 'dumpFilename' which gets written to when a connection cannot be established to
the
SocketServer.
For example:
appender name=SOCKSERV class=com.db.gmr.core.log.SocketAppender
On numerous occasions users have complained about deadlocks after
introducing log4j into their code. However, without exception the bug
was always in the application code not in log4j. Log4j may well
contain concurrency-related bugs but we need proof not vague
suspicions. Since you indicate
Ceki,
Please find my comments interspersed
| On numerous occasions users have complained about deadlocks after
| introducing log4j into their code. However, without exception the bug
| was always in the application code not in log4j. Log4j may well
| contain concurrency-related bugs but we need
-all
I can reassure all that the fault is *not* in the roll-strategy/algorithms.
It was not a concurrency bug in my own code either, but rather a combination
of rolling and the class
LOG4J_HOME/contribs/JimMoore/LoggingOutputStream.java. I'm probably not the
first one to fall into this trap.
I
Anybody have an appender that emits SNMP messages?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi, all.
I am confused on SocketServer.
On SocketServer's main, it calls configureHierarchy() to find the hierarchy for the IP
address. If ip address's LCF is not found, then it would generate a default
hierarchy. I am not quite sure about hierarchy, that all I know is it sets the
priority
Hi Mark,
I am using the FileWatchdog and PropertyConfigurator as suggested by u. But I am not able to fix the puzzle. What I have now is individual parts and need your advice on placing things together.
I want to use RollingFileAppender with run-time configuration of the debug, errors and info
I am also interested in this appender as we have a requirement to generate
these messages.
Mark Masterson [EMAIL PROTECTED]@compuserve.com on
28/09/2001 04:47:56
Please respond to LOG4J Users Mailing List
[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
To: LOG4J Users Mailing List
Thomas et. al,
Thanks for the good news about finding the bug.
I also believe that LogLog stuff is unclean (since it more or less
duplicates the errorHandler functionality) and should be removed as soon as
someone gets around to resolving any remaining difficulties in moving those
16 matches
Mail list logo