Re: IBM Websphere Portal - log4j log file is empty!

2005-08-29 Thread Jacob Kjome
Quoting Kalpeshkumar Soni <[EMAIL PROTECTED]>: > Hi > I am facing a strange problem > 1) My log4j jar is in java/lib directory and is loaded by bootstrap loader > 2) My log4j.xml is loaded properly > The log4j.log file is created, but the file remains empty > I do not get any errors/exceptions

How to use the JMSAppender for Chainsaw/Log4j

2005-08-29 Thread Rakesh Patel
I am trying to configure chainsaw/log4j to use the JMSAppender. I am unable to follow the javadoc for the JMSAppender. Can anyone tell me how to configure the JMSAppender with Sonic MQ? An example would be most illuminating! Rakesh -

RE: Chainsaw: Merge log files

2005-08-29 Thread Scott Deboy
Yes you can 'merge' logs in Chainsaw V2. You need to add a 'plugin' (receiver configuration) in the Chainsaw config file for each source you want to see in Chainsaw. Chainsaw is a tab-based app - as events are received, each event is 'routed' to a tab based on the content of the logging event. T

IBM Websphere Portal - log4j log file is empty!

2005-08-29 Thread Kalpeshkumar Soni
Hi I am facing a strange problem 1) My log4j jar is in java/lib directory and is loaded by bootstrap loader 2) My log4j.xml is loaded properly The log4j.log file is created, but the file remains empty I do not get any errors/exceptions in SystemOut.log / SystemErr.log except I see this one in S

RE: LogFilePatternReceiver

2005-08-29 Thread Scott Deboy
LogFilePatternReceiver relies on the ORO library - add it to your classpath and everything should work fine. Scott -Original Message- From: news [mailto:[EMAIL PROTECTED] On Behalf Of Rakesh Patel Sent: Monday, August 29, 2005 12:14 PM To: log4j-user@logging.apache.org Subject: LogFilePat

LogFilePatternReceiver

2005-08-29 Thread Rakesh Patel
i downloaded the chainsaw v2 package, loaded the example chainsaw configuration file. the odd thing is i am unable to instaniate the LogFileReceiver receiver. the chainsaw console window shows the following exception: LOG4J-INTERNAL: 2005-08-29 15:09:15,202 ERROR [Thread-7] org.apache.log4j.help

Re: R: Multiple log4j.properties

2005-08-29 Thread Jacob Kjome
Quoting Fabrizio Squittieri <[EMAIL PROTECTED]>: > So if i have a log4j.jar in any webapp i can say that their log4j.properties > are completely independent? > > And i shouldn't mind if someone puts a log4j.rootLogger=DEBUG,stdout > somewhere in any log4j.properties? > > I don't know but it seems

Chainsaw Configuration Questions

2005-08-29 Thread Rakesh Patel
I have multiple applications running on multiple boxes(solaris/linux) across our network. There will be multiple instances of chainsaw running on multiple client pcs - the chainsaw clients can come up at any time and be shutdown anytime. so i want is: 1. each chainsaw user have the ability to

FW: Log4J date/time output problem

2005-08-29 Thread oops
Hello. I also have the below problem. I don't use ASYNC file appender I just use DailyRollingFIleAppender. My log4j.properties is below.. == log4j.appender.R=org.apache.log4j.DailyRollingFileAppender log4j.appender.R.File=/home1

Re: R: Multiple log4j.properties

2005-08-29 Thread Bruno Melloni
As I mentioned in my previous reply... it depends on the version of Tomcat. If you are having this problem, solutions exist. Here are a couple of ideas to explore, one of them might help you: a) You might want to name the properties differently for each application (for example: app1Log4j.pro

calling NDC.get() directly

2005-08-29 Thread David . Johnson
Dear, I've seen in the javadoc of the NDC class that the get() method should not be called directly. Why is this? We would like to get alle messages from the NDC stack without having a looging event. Is there another (clean) way? Greetings, David Johnson

Re: Multiple log4j.properties

2005-08-29 Thread Bruno Melloni
A word of caution. I am not sure that every version of Tomcat behaves that well. JBoss (based on Tomcat for the web serving portion) had problems with the isolation issue in several of its older versions (roughly around the time of Tomcat 5.0) and claimed that its problems were inherited from To