Logback DBAppender具有null caller_filename

时间:2013-06-04 13:12:33

标签: java mysql jndi logback context.xml

使用logback-1.0.13.jar和JDK 1.6u34。

我有一个Java Web应用程序(WAR),其中包含以下WEB-INF/classes/logback.xml

<configuration debug="true" scan="true" scanPeriod="5 minutes">
    <appender name="logManager-dbAppender" class="ch.qos.logback.classic.db.DBAppender">
        <filter class="ch.qos.logback.classic.filter.LevelFilter">
            <level>INFO</level>
            <onMatch>ACCEPT</onMatch>
            <onMismatch>NEUTRAL</onMismatch>
        </filter>
        <filter class="ch.qos.logback.classic.filter.LevelFilter">
            <level>WARN</level>
            <onMatch>ACCEPT</onMatch>
            <onMismatch>NEUTRAL</onMismatch>
        </filter>
        <filter class="ch.qos.logback.classic.filter.LevelFilter">
            <level>ERROR</level>
            <onMatch>ACCEPT</onMatch>
            <onMismatch>DENY</onMismatch>
        </filter>
        <connectionSource class="ch.qos.logback.core.db.JNDIConnectionSource">
            <jndiLocation>java:comp/env/jdbc/dbLogging-local</jndiLocation>
        </connectionSource>
    </appender>

    <root level="ALL">
        <appender-ref ref="logManager-dbAppender" />
    </root>
</configuration>

以下${TOMCAT_HOME}/conf/context.xml(所有网络应用的全局context.xml):

<Context>
    <WatchedResource>WEB-INF/web.xml</WatchedResource>

    <Resource
        name="jdbc/dbLogging-local"
        auth="Container"
        type="javax.sql.DataSource"
        driverClassName="com.mysql.jdbc.Driver"
        url="jdbc:mysql://my-mysql-server.example.com:3306/my_db"
        username="my_user"
        password="my_password"

        maxActive="20"
    />
</Context>

WEB-INF/lib/mysql-jdbc-5.1.25.jar上的运行时类路径上有latest MySQL/JDBC driver。另外,因为这是一个全局context.xml,我在${TOMCAT_HOME} / lib也有相同的MySQL / JDBC驱动程序。

我得到以下堆栈跟踪:

08:54:52,905 |-ERROR in ch.qos.logback.classic.db.DBAppender[logManager-dbAppender] - problem appending event com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Column 'caller_filename' cannot be null
    at com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Column 'caller_filename' cannot be null
    at  at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at  at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    at  at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at  at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
    at  at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
    at  at com.mysql.jdbc.Util.getInstance(Util.java:386)
    at  at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1040)
    at  at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4096)
    at  at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4028)
    at  at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2490)
    at  at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2651)
    at  at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2734)
    at  at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2155)
    at  at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2458)
    at  at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2375)
    at  at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2359)
    at  at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
    at  at org.apache.tomcat.dbcp.dbcp.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:105)
    at  at ch.qos.logback.classic.db.DBAppender.subAppend(DBAppender.java:105)
    at  at ch.qos.logback.classic.db.DBAppender.subAppend(DBAppender.java:42)
    at  at ch.qos.logback.core.db.DBAppenderBase.append(DBAppenderBase.java:108)
    at  at ch.qos.logback.core.UnsynchronizedAppenderBase.doAppend(UnsynchronizedAppenderBase.java:88)
    at  at ch.qos.logback.core.spi.AppenderAttachableImpl.appendLoopOnAppenders(AppenderAttachableImpl.java:48)
    at  at ch.qos.logback.classic.Logger.appendLoopOnAppenders(Logger.java:272)
    at  at ch.qos.logback.classic.Logger.callAppenders(Logger.java:259)
    at  at ch.qos.logback.classic.Logger.buildLoggingEventAndAppend(Logger.java:441)
    at  at ch.qos.logback.classic.Logger.filterAndLog_0_Or3Plus(Logger.java:395)
    at  at ch.qos.logback.classic.Logger.info(Logger.java:599)
    at  at com.myapp.server.DummyServlet.doGet(Unknown Source)
    at  at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
    at  at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
    at  at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
    at  at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
    at  at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233)
    at  at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
    at  at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
    at  at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
    at  at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
    at  at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:298)
    at  at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859)
    at  at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:588)
    at  at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489)
    at  at java.lang.Thread.run(Thread.java:662)

关于为什么我得到MySQL异常的任何想法?我在Old Nabble上找到了this similar unanswered question,我想知道这是一个长期存在的错误......?

它似乎连接到我的MySQL服务器并在(根据Logback DBAppender的onw DDL)插入NULL logging_event.caller_filename时,该列上不允许使用NULL。

提前致谢!

1 个答案:

答案 0 :(得分:0)

我和PostgreSQL以及slf4j 1.6.6的logback 1.0.7有类似的问题 不知怎的,似乎调用者信息没有“总是”传递导致这个问题,这反过来意味着相关的日志调用不会对数据库产生(如果在logback配置上没有debug =“true”,你就不要甚至不知道。)

作为虚拟解析,可以放宽日志记录表中的数据库列约束(在调用者列中不需要“not null”)。然而,在我的情况下,事实证明我如何在代码中构造记录器实例:虽然这导致了上述失败

import org.slf4j.Logger;
import org.slf4j.LoggerFactory;

Logger log = LoggerFactory.getLogger(My.class);

这很好(即填写了来电者信息)

Logger log = LoggerFactory.getLogger(My.class.getName());

我无法解释它。