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] Resolved: (CAMEL-3560) Detect uncaught exceptions in UoWProcessor to ensure UoW is done even for those uncaught exceptions
Date Wed, 19 Jan 2011 11:20:44 GMT

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

Claus Ibsen resolved CAMEL-3560.
--------------------------------

    Resolution: Fixed

trunk: 1060768.

> Detect uncaught exceptions in UoWProcessor to ensure UoW is done even for those uncaught
exceptions
> ---------------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-3560
>                 URL: https://issues.apache.org/jira/browse/CAMEL-3560
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>    Affects Versions: 2.5.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 2.6.0
>
>
> The Camel routing engines will handle this in 99.9% of the cases, but when you shutdown
a Spring AC then Spring may stop beans in whatever order and this can cause those beans to
fail operating during a graceful shutdown. And in worst case exceptions is thrown in situations
where they are not normally done.
> To cater for that and other situations the UoWProcessor should detect this and act accordingly.
> This ensure the in flight registry will be tracked and we are not stuck with a missing
inflight message, causing Camel to wait for the 300 sec timeout to shutdown.
> For example just try hitting ctrl + c in that camel-example-management and you can see
such an example.

-- 
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