[logback-dev] [JIRA] Commented: (LBCLASSIC-157) Add option to include caller data in JMS Appender or to disable caller data in DB Appender

[Ralph Goers (JIRA)]

    [ http://jira.qos.ch/browse/LBCLASSIC-157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11330#action_11330 ] 

Ralph Goers commented on LBCLASSIC-157:
---------------------------------------

DBAppender checks to see if callerData is null and does not call stmt.setString() if it is. However, the SQL statement always includes the callerData fields. My understanding is that not calling a set method for a parameter will result in an SQLException. So DBAppender should either have two flavors of the insert statement or the callerData bind variables should always be set to something.

> Add option to include caller data in JMS Appender or to disable caller data in DB Appender
> ------------------------------------------------------------------------------------------
>
>                 Key: LBCLASSIC-157
>                 URL: http://jira.qos.ch/browse/LBCLASSIC-157
>             Project: logback-classic
>          Issue Type: New Feature
>          Components: appender
>    Affects Versions: 0.917
>            Reporter: Ging Ming Chan
>            Assignee: Logback dev list
>            Priority: Minor
>
> We are using the JMSQueueAppender remotely with a centralised server that uses the DBAppender to log to the database.  However, since the JMSQueueAppender does not send the caller data, and the DBAppender always expect it, the operation never succeeded.
> There are two options to fix this, either add the includeCallerData option in the JMS Appender or to exclude caller data in the DB Appender.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira