[
https://issues.apache.org/jira/browse/CAMEL-9872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-9872:
----------------------------------
Assignee: Claus Ibsen
> VetoCamelContextStartException with rethrowException=false cases MainSupport
> class to hang
> ------------------------------------------------------------------------------------------
>
> Key: CAMEL-9872
> URL: https://issues.apache.org/jira/browse/CAMEL-9872
> Project: Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.17.0
> Reporter: Jimi Hullegård
> Assignee: Claus Ibsen
> Priority: Minor
>
> Hi,
> I just created my own LifecycleStrategy implementation, that performs some
> sanity checks on context startup, and throws a VetoCamelContextStartException
> if it detects a problem. But since I only want a user friendly error message
> to be printed, and no stack trace, I opted to have rethrowException=false.
> That caused Camel to abort the start of the context. But it keeps the process
> running, instead of letting it terminate. If I use rethrowException=false the
> process terminates as expected.
> When debugging this in Eclipse, I see that Camel get stuck in the method
> waitUntilCompleted() in org.apache.camel.main.MainSupport.
> I use Apache Camel 2.17.0, Camel Spring (XML), and start the process using
> org.apache.camel.spring.Main. When asking about this behaivor in the user
> mailing list, Claus Ibsen hinted that this is a bug that I should report
> here. Apparently the Main class doesn't handle the veto properly.
> Regards
> /Jimi
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
