Hi all,
I am using Tomcat 4.1.27 + log4j 1.2.8+Win2k sp4. I have some problems
with it.
1, Log4j locks the log file so that I cannot clear the content of the file.
After some time I want to delete old debugging data while development.
Currently I am doing it by shutting down Tomcat. It is
Hi All,
I have a client that sends a heartbeat to the server every 30 seconds. If
the client is unable to connect to the server it prints the message along
with the stack trace. This failure may persist for a while and there is a
risk of filling up the log files. If I just note the failure, there
I need to access the backup appender in the fallback error handler of a primary
appender, but there is no method to
access it and the appender is package private. I have subclassed the
FallbackErrorHandler class to redefine the
setBackupAppender method and added a getBackupAppender method.
Hello Milind,
FallbackErrorHandler was not designed/intended to be sub-classed. Hence,
the private accessor. If you think there is value in sub-classing
FallbackErrorHandler we can certainly accomodate your wish. A patch would
be handy!
I hope this answers your question,
At 06:32 PM
The problem is how to determine if a message is a duplicate?
Is there any API that lets me read all the events that have occurred in last
30 seconds, whereby I can do the comparison and leave out stack trace of
duplicate messages.
One way would be to create your own Log class which has a unique
1, Log4j locks the log file so that I cannot clear the content of the file.
1. You could use rolling files and delete the old ones, or even better, upgrade
to linux :-)
2, Is it necessary to initialise log4j through a servlet ?.
No. It can be done in a jsp also, if that is what you mean, ie:
There isn't an API where you can access a set of previous messages.
However, Ceki describes a good approach in his book.
You can create a Filter that hangs on to the previous LogEvent and
suppresses an incoming LogEvent if it is a duplicate. There is nothing to
prevent you from buffering n
Just a suggestion, it would be a good idea to use a RollingFileAppender
rather than logging everything to one big file. You'll have no problems
deleting the files that have rolled over.
-Original Message-
From: Antony Paul [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 17, 2003
At 04:53 PM 12/17/2003 +0530, Antony Paul wrote:
Hi all,
I am using Tomcat 4.1.27 + log4j 1.2.8+Win2k sp4. I have some problems
with it.
1, Log4j locks the log file so that I cannot clear the content of the file.
After some time I want to delete old debugging data while development.
You can
We are seeing a dead lock problem, during load test. Has anyone seen this before. Is
there any patch for this issue.
I have attached a sample log below.
Any help greatly appreciated.
Thanks - Prithi
ExecuteThread: '14' for queue: 'JmsDispatcher' daemon prio=5 tid=0x2f8f88 nid=0x38
We are trying to use Log4J in our Struts app (we are using JDK 1.3).
But we keep getting errors.
Can anyone help us?
-
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing
You need to do a LogManager.shutdown() upon application shutdown. That will
solve problems with Log4j keeping handles on files. Use a Servlet Context
Listener for this.
Jake
Quoting Antony Paul [EMAIL PROTECTED]:
Hi all,
I am using Tomcat 4.1.27 + log4j 1.2.8+Win2k sp4. I have some
the log4J jar file clashes with the commons logging jar file (struts)...
if we remove the commons logging jar, the app won't run b/c some classes are missing.
We don't know if we can even use Log4J with JDK 1.3
Does anyone know?
Can anyone help?
Jacob Kjome [EMAIL PROTECTED] wrote:
What does this mean?
I am new to this...can anyone explain?
[EMAIL PROTECTED] wrote:
Your BuddyScript Server is not connected to BSCS! For instructions, see
http://bscs.buddyscript.com/log4j-user/
Build your own interactive agent! Download BuddyScript SDK for FREE today at
For me, Log4J works just fine with J2SE 1.3.x, and 1.4.x on
W2K, WXP, and Linux 7.2 (Sun, JDK runtimes).
At 05:21 PM 12/17/2003, you wrote:
the log4J jar file clashes with the commons logging jar file (struts)...
if we remove the commons logging jar, the app won't run b/c some classes
are
I am using the JMSQueueAppender (from the contributions) in a webapp that is deployed
on Tomcat 4.1 using Sun's jdk 1.4. When I try to write to this appender, I get the
following exception:
log4j:ERROR Could not get initial context with
[com.ibm.websphere.naming.WsnInitialContextFactory] and
16 matches
Mail list logo