[
https://issues.apache.org/activemq/browse/CAMEL-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-283.
--------------------------------
Resolution: Fixed
Fix Version/s: 1.3.0
patch is applied with thanks.
> DeadLetterChannel - logging improvements when exchange handled by dead letter
> -----------------------------------------------------------------------------
>
> Key: CAMEL-283
> URL: https://issues.apache.org/activemq/browse/CAMEL-283
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 1.2.0
> Reporter: Claus Ibsen
> Assignee: Willem Jiang
> Priority: Trivial
> Fix For: 1.3.0
>
> Attachments: camel_283_patch.txt
>
>
> The submitted patch have these improvements to the logger in
> deadletterchannel for delivery attempts
> - outputs exchange id so we can correlate the lines in the log files.
> - now also logs when the exchange could not be delivered and was handled by
> the failure processer (usually a deadletterchannel)
> - minor issues with existing debug logging when sleeping (now also output
> millis) to be in line with other similar log lines in Camel
> I have not outputted the exchange itself (exchange.toString()) when the
> delivery could not be delivered successfully since there could be sensitive
> data in the exchange (e.g. an invoice input message) that we do not want to
> be logged in our log.
> But I think the logging of the exchange id is a good improvement and that
> they are aligned in the same position in the logline so it's easier to
> grep/find in the logs when you investigate and incident.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
