Not sure if this is exactly your problem, but I've seen this in the past
with other open source products. It comes from a conflict in log4j (if
you're not using log4j, then this is not your problem/solution.) In your
log4j.properties, you've probably set the log level to INFO or DEBUG,
etc. You'll need another entry as follows:
log4j.category.org.apache.tapestry=FATAL
This may not be exact, so if it doesn't work, check out the log4j
website for the proper configuration, but that should be close...
Frank Russo
Senior Developer
FX Alliance, LLC
-----Original Message-----
From: Lennart Benoot [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 07, 2005 7:44 AM
To: [email protected]
Subject: Extreme lots of logging
Hi all,
Yesterday, all of a sudden, my Tapestry application started to produce
extremely lots of logging. This slows down the system significantly. The
stack is Tapestry / Tomcat / Eclipse.
I don't now exactly where the problem should be searched but it seams
like tapestry classes are generating most of the logging. Anyone had the
same problems? Any idea how to solve this problem?
Regards,
Lennart
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
