17:02:43,325 |-ERROR in ch.qos.logback.classic.db.DBAppender[DB] - problem appending event java.lang.ArrayIndexOutOfBoundsException: 0
at java.lang.ArrayIndexOutOfBoundsException: 0
at at ch.qos.logback.classic.db.DBAppender.bindCallerDataWithPreparedStatement(DBAppender.java:167)
at at ch.qos.logback.classic.db.DBAppender.subAppend(DBAppender.java:104)
at at ch.qos.logback.classic.db.DBAppender.subAppend(DBAppender.java:43)
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.core.AsyncAppenderBase$Worker.run(AsyncAppenderBase.java:226)
Specifically, I have a DBAppender which works fine normally, but, if I wrap it in an AsyncAppender, it fails. If I enable the caller data on the async appender, it works again, which I believe is the same as this issue.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
at java.lang.ArrayIndexOutOfBoundsException: 0
at at ch.qos.logback.classic.db.DBAppender.bindCallerDataWithPreparedStatement(DBAppender.java:167)
at at ch.qos.logback.classic.db.DBAppender.subAppend(DBAppender.java:104)
at at ch.qos.logback.classic.db.DBAppender.subAppend(DBAppender.java:43)
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.core.AsyncAppenderBase$Worker.run(AsyncAppenderBase.java:226)
Specifically, I have a DBAppender which works fine normally, but, if I wrap it in an AsyncAppender, it fails. If I enable the caller data on the async appender, it works again, which I believe is the same as this issue.