camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Preben Asmussen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-9772) Make it easier to turn on/off logExhaustedMessageBody
Date Sun, 10 Apr 2016 08:04:25 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-9772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15233974#comment-15233974
] 

Preben Asmussen commented on CAMEL-9772:
----------------------------------------

I have started looking at it. 
The change seems to spread over Camel Core + jmx management, camel-spring, blueprint and possible
also camel-spring-boot. 
Maybe I should do a pr on what i have now since I'm not sure I have identified all places
that needs changes. Then we can take it from there.

Also the test is a bit hard to write since it's only affecting the log output. 
I found on existing test DeadLetterChannelLogExhaustedMessageHistoryWithBodyTest, but this
seems actually not to do whats expected (logging the messagehistory with body) since the flag
shouldRedeliver is always set to true when calling logFailedDelivery on the RedeliveryErrorHandler.


> Make it easier to turn on/off logExhaustedMessageBody
> -----------------------------------------------------
>
>                 Key: CAMEL-9772
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9772
>             Project: Camel
>          Issue Type: Improvement
>            Reporter: Preben Asmussen
>            Priority: Minor
>             Fix For: 2.18.0
>
>
> Make logExhaustedMessageBody an option on CamelContext to turn on/off header and message
body logging. Default should be false.
> See http://camel.465427.n5.nabble.com/setting-logExhaustedMessageBody-in-Spring-xml-td5779942.html




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message