unable to debug log4j

Ranch Hand

Posts: 97

posted 20 years ago

Number of slices to send:

Optional 'thank-you' note:

Send

I am unable to debug log4j as it is not giving any exception and even not logging

the configuration file is as follows

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE log4j:configuration SYSTEM "log4j.dtd">
<log4j:configuration xmlns:log4j="http://jakarta.apache.org/log4j/">
        <appender name="JDBC" class="org.apache.log4j.jdbcplus.JDBCAppender">
                <param name="url" value="jdbc:mysql://localhost:3306/CIISLEIFSUDB" />
                <param name="username" value="soni" />
                <param name="password" value="soni123" />
                <param name="sql" value="Insert into LeifSupCmdHist (SessionId, CommandId, Time, TermId, OldData, NewData, Result) values('@NDC@', '@MDC:CmdId@', NULL, '@MDC:TermAdd@', '@MDC:In@', '@MDC  :-o	  ut@', '@MDC:Result@')"/>
                <param name="buffer" value="1"/>
                <param name="commit" value="true"/>
                <param name="dbclass" value="com.mysql.jdbc.Driver"/>
        </appender>
        <appender name="SYSTEMOUT" class="org.apache.log4j.ConsoleAppender">
                <param name="target" value="System.out"/>
                <layout class="org.apache.log4j.PatternLayout">
                        <param name="ConversionPattern" value=" %d{dd.MM.yyyy HH:mm:ss} - %m\n"/>
                </layout>
        </appender>
 
        <root>
                
                <appender-ref ref="JDBC"/>
        </root>
 
</log4j:configuration>

and jsp code is

configuration file and jsp file accessing it are in the same directory

soni.
[ April 28, 2005: Message edited by: Soni Prasad ]

SCJP 1.4, SCBCD 1.3

Carol Enderlin

drifter

Posts: 1364

posted 20 years ago

Number of slices to send:

Optional 'thank-you' note:

Send

log4j generally won't throw exceptions, that's a feature.

You can pass in "-Dlog4j.debug" to get it to print out its own debug. See log4j manual. On command-line it's just java -Dlog4j.debug. You don't mention your container/server they differ in what kind of options are easily passed in to the startup scripts.

Or put it in the configuration file (but since it's probably not finding your config file that may not help initially, in xml file it looks like <log4j:configuration debug="true" ...)

Regarding your no logging problem, it probably cannot find the file soni.xml. There's a servlet example in the manual. Or leave out the call to configure() and just put the file named log4j.xml in the classpath.

With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.