[JIRA] Created: (LBCLASSIC-157) Add option to include caller data in JMS Appender or to disable caller data in DB Appender
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
[ http://jira.qos.ch/browse/LBCLASSIC-157?page=com.atlassian.jira.plugin.syste... ] 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
[ http://jira.qos.ch/browse/LBCLASSIC-157?page=com.atlassian.jira.plugin.syste... ] Ceki Gulcu reassigned LBCLASSIC-157: ------------------------------------ Assignee: Ceki Gulcu (was: Logback dev list)
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: Ceki Gulcu 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
[ http://jira.qos.ch/browse/LBCLASSIC-157?page=com.atlassian.jira.plugin.syste... ] Ceki Gulcu updated LBCLASSIC-157: --------------------------------- Priority: Major (was: Minor)
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: Ceki Gulcu
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
[ http://jira.qos.ch/browse/LBCLASSIC-157?page=com.atlassian.jira.plugin.syste... ] Michael Schechter commented on LBCLASSIC-157: --------------------------------------------- We are also having this issue. There appear to be a couple of additional options for implementation: 1) Log4J's JMS appender has a configuration parameter that tells the appender to include the location/caller information; this could be implemented in Logback 2) The classic DBAppender allows configuration of a DBNameResolver for custom table structures; the JMS appender could be modified in a similar fashion to allow a PreSerializationTransformer injection so that the logic could be customized that way 3) The LoggingEventVo.build() method could be changed to always pull the caller data I'm hoping this can get fixed fairly soon; we can work around it by creating a custom appender to force the caller information generation in the near term.
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: Ceki Gulcu
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
participants (4)
-
Ceki Gulcu (JIRA) -
Ging Ming Chan (JIRA)
-
Michael Schechter (JIRA)
-
Ralph Goers (JIRA)