![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
1.0.9 |
|
Assignee:
|
Logback dev list
|
|
Components:
|
logback-classic |
|
Created:
|
21/Feb/13 11:45 PM
|
|
Description:
|
The DBAppender throws an exception if caller data is null on an event.
This happens in ch.qos.logback.classic.db.DBAppender.bindCallerDataWithPreparedStatement() at line 165.
We have a scenario where various web-sites are sending log events to a common remote "SocketServer" (using ch.qos.logback.classic.net.SocketAppender). They all use the option: <includeCallerData>false</includeCallerData>
The common socket server writes to file, but we wanted to try adding a DbAppender there and got an exception.
Hacking the code to check for callerdata[0] and to set the SQL parms to default values, got around the problem.
|
|
Project:
|
logback
|
|
Labels:
|
dbappender
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Darius X.
|
|
|
|
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
|
_______________________________________________
logback-dev mailing list
[email protected]
http://mailman.qos.ch/mailman/listinfo/logback-dev
