[
https://issues.apache.org/jira/browse/CAMEL-4754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-4754:
-------------------------------
Affects Version/s: (was: 2.9.0)
2.8.3
Fix Version/s: 2.9.0
Issue Type: Bug (was: Improvement)
Its a bug in the error handler when using context scoped onException.
When the routes is built, then the error handler is mixed in the routes (Camel
2.x architecture), and in this logic error handlers is build based on the given
route built, and a reference is stored in the context scoped OnException.
However that reference should have been keyed to the given created route. This
ensures when Camel picks the OnException to handle the exception that occurred,
it should pick the error handler that matches the current route. Beforehand it
will pick the last created error handler from the last created route. All
though the error handler reacts similar, it was only the Log DSL that uses the
route id in the log process, and thus that route id was wrong, causing the Log
processor to log the wrong id.
> The onException clause should make use of the correct logger name given
> through the log DSL
> --------------------------------------------------------------------------------------------
>
> Key: CAMEL-4754
> URL: https://issues.apache.org/jira/browse/CAMEL-4754
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.8.3
> Reporter: Babak Vahdat
> Assignee: Claus Ibsen
> Priority: Minor
> Fix For: 2.9.0
>
> Attachments: debugger.jpg
>
>
> See
> http://camel.465427.n5.nabble.com/global-onException-clause-wrongly-identifies-route-in-which-exception-occurs-log-name-td5058304.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
