camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CAMEL-283) DeadLetterChannel - logging improvements when exchange handled by dead letter
Date Sat, 05 Jan 2008 14:15:43 GMT

     [ https://issues.apache.org/activemq/browse/CAMEL-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Claus Ibsen updated CAMEL-283:
------------------------------

    Attachment: camel_283_patch.txt

The patch.

I have faxed and signed the Apache CLA 2-3 years ago (my name is on the list, but I do not
recall when the list is on the apache site).

> 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
>            Priority: Trivial
>         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.


Mime
View raw message