[jira] [Resolved] (CAMEL-4574) Tracer - Should have a fixed limit of maxChars to avoid tracing to big message bodies

["Claus Ibsen (Resolved) (JIRA)" <ji...@apache.org>]

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

Claus Ibsen resolved CAMEL-4574.
--------------------------------

    Resolution: Fixed

The log and tracer now have a default maxChars at 10000
                
> Tracer - Should have a fixed limit of maxChars to avoid tracing to big message bodies
> -------------------------------------------------------------------------------------
>
>                 Key: CAMEL-4574
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4574
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.9.0
>
>
> The tracer
> http://camel.apache.org/tracer
> Has a tracer formatter that has maxChars set as unlimited by default. We should change this to a value of lets say 10000 chars (10K) or possible higher (100K) but that is also a lot considering you would normally log the tracer events.
> Then maxChars = -1 and 0 can become unlimited as its now. 
> Notice maxChars is the entire logging line, including headers, node ids etc, its (all inclusive). So if you configure maxChars=0, then nothing is outputted from the trace formatter. So maxChars = 0 should be as now, the current behavior, is unlimited.
> See nabble
> http://camel.465427.n5.nabble.com/tracing-large-messages-tp4921360p4921360.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira