[
https://issues.apache.org/jira/browse/CAMEL-11360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-11360.
---------------------------------
Resolution: Fixed
We can later implemented a better tracer if you turn on tracing - intended for
development purpose.
The old stuff is deprecated.
> Optimise - Disable Tracer and use BacklogTracer instead
> -------------------------------------------------------
>
> Key: CAMEL-11360
> URL: https://issues.apache.org/jira/browse/CAMEL-11360
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.20.0
>
> Attachments: after.png, before.png
>
>
> See CAMEL-11359
> We have the old tracer logic that is cruft. Its still capturing tracing
> details during runtime, but that is obsolete with the message history we use
> instead (eg the stuff that also dumps those route stacktrace errors).
> So if users say camelContext.setTracing(true) we can then use BacklogTracer
> instead to log similar trace events.
> This allows us to not capture 2x trace details during routing as message
> history will be used for both.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
