Re: creating log files which are readable for Chainsaw

Thanks, I've solved the problem. It seems that both the SocketAppender and the XmlAppender needs to turn on the LocationInfo in their config files to send and catch the LocationInfo... Bence Scott Deboy wrote: Add a consoleappender to the socketserver config which prints line, method, etc.

recovery of JDBCAppender

Hi All, I am using org.apache.log4j.jdbc.JDBCAppender in my app. The app runs on JBoss and I have directly given the DB credentials in log4j.xml. Once in a while, the DB crashes or the network goes down and the JDBCAppender fails, which is expected. But when the connection is restored, the

Re: recovery of JDBCAppender

I have also seen this situation and am looking for a workaround. -erik On Dec 18, 2006, at 3:02 PM, Prasanth Ramachandran wrote: Hi All, I am using org.apache.log4j.jdbc.JDBCAppender in my app. The app runs on JBoss and I have directly given the DB credentials in log4j.xml. Once in a

logging to different files depending on class

I would like to send my logging output to different log files from 3 different java classes, all in the same package. Would someone please point me to where I can find info/examples of how to do this? Thanks, TimB - To

Sandro Ruch/namics/com is out of the office.

I will be out of the office starting 18.12.2006 and will not return until 02.01.2007. I will respond to your message when I return. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL

quesiton about LoggingEvent

Hi: I use the following code Class testClass { public void test1() { --- Throwable throwable = null; Throwable child = new Throwable(test); LoggingEvent loggingEvent = new LoggingEvent(this.getClass().getName(),testLogger,Level.DEBUG,logMsg,child); System.out.println(class =

JDBCAppender with large message values

Hi, I want to include the JDBCAppender as one of our appenders so that all error level messages will be written to a common database. The problem is that the message content frequently contains a stack trace which is too large for the database column. What I get right now is a row with the

RE: logging to different files depending on class

Hi Tim, If you log to loggers that are named after the classes you're logging from (which is the most common convention for naming loggers), you can simply use three different file appenders that you attach to the loggers corresponding to your classes. This is basic log4j, have a read through