I've seen this problem happen when the log4j.properties file is no longer on the classpath (in the case of it being accidentally excluded from my .war file during an ant build). Also, I seem to recall some classpath order problem with Eclipse where this had happened. I basically had to rearrange the export order of the commons-logging and/or log4j .jar files.
On 3/8/06, Engel, Gregory A <[EMAIL PROTECTED]> wrote:
Not really an Ibatis question per se but I'm sure someone here has seen this....log4j:WARN No appenders could be found for logger (java.sql.Connection).
log4j:WARN Please initialize the log4j system properly.My log4j.properties file looks like....# Set root logger level to DEBUG and its only appender to A1.
log4j.rootLogger=INFO, Appender1
log4j.appender.Appender1=org.apache.log4j.ConsoleAppender
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout# A1 uses PatternLayout.
log4j.appender.Appender1.layout=org.apache.log4j.PatternLayout
log4j.appender.Appender1.layout.ConversionPattern=%-5p %-25C{1}: %m%n#log4j.rootCategory=DEBUG, Chainsaw
#log4j.appender.Chainsaw=org.apache.log4j.net.SocketAppender
#log4j.appender.Chainsaw.remoteHost=localhost
#log4j.appender.Chainsaw.port=4445
#log4j.appender.Chainsaw.locationInfo=truelog4j.logger.com.ibatis=DEBUG
log4j.logger.java.sql.PreparedStatement=DEBUG
log4j.logger.java.sql.Statement=DEBUG
log4j.logger.com.ibatis.common.jdbc.SimpleDataSource=DEBUG
log4j.logger.java.sql.ResultSet=DEBUG
log4j.logger.java.sql.Connection=DEBUGThis used to work fine but somewhere along the line it stopped working.
