Java Logback DBAppender的调用者文件名为空

使用

logback-1.0.13.jar

和JDK1.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>

并在我的运行时类路径上的

WEB-INF/lib/mysql-jdbc-5.1.25.jar

）。此外，因为这是一个全局的

context.xml

，所以我还有相同的MySQL/JDBC驱动程序，位于

${TOMCAT_HOME}

/lib

我得到了以下堆栈跟踪：

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上发现了，我想知道这是否是一个长期存在的bug

它似乎正在连接到我的MySQL服务器并插入一个空

日志记录\u事件。当（根据Logback DBAppender的onw DDL）该列上不允许空值时，调用者\u文件名

---

提前谢谢

我在PostgreSQL和logback 1.0.7以及slf4j 1.6.6上也遇到过类似的问题 不知何故，似乎并没有“始终”传递调用方信息，这导致了这个问题，这反过来意味着相关的日志调用不会对数据库进行调用（如果在logback配置中没有debug=“true”，您甚至不知道它）

作为虚拟解析，可以放松日志表中的数据库列约束（不需要调用方列中的“NOTNULL”）。然而，在我的例子中，我发现如何在代码中构造记录器实例很重要：这导致了上述失败

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

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

这样做效果很好（即填写了呼叫者信息）

但我无法解释

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

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

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