[
https://issues.apache.org/jira/browse/CAMEL-12843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16633178#comment-16633178
]
Freeman Fang commented on CAMEL-12843:
--------------------------------------
Attached a proposal fix.
[~davsclaus], is this change OK, would it affect other cases outside Karaf? Or
instead of the RuntimeException, shall we just resume a suspended camelcontext
when even users use start command?
Thanks!
> CamelContext Start command shouldn't start a Suspended context
> --------------------------------------------------------------
>
> Key: CAMEL-12843
> URL: https://issues.apache.org/jira/browse/CAMEL-12843
> Project: Camel
> Issue Type: Bug
> Reporter: Freeman Fang
> Priority: Major
> Attachments: CAMEL-12843.patch
>
>
> We found this problem in Karaf camel command, but think it should also exist
> in other camel command usecases.
> In Karaf
> {code}
> karaf@root()> camel:context-list
> Context Status Total # Failed # Inflight #
> Uptime
> ------- ------ ------- -------- ----------
> ------
> camel-1 Started 0 0 0
> 1.366 seconds
> karaf@root()> camel:context-suspend camel-1
> karaf@root()> camel:context-list
> Context Status Total # Failed # Inflight #
> Uptime
> ------- ------ ------- -------- ----------
> ------
> camel-1 Suspended 0 0 0
> 7.554 seconds
> karaf@root()> camel:context-start camel-1
> karaf@root()> camel:context-list
> Context Status Total # Failed # Inflight #
> Uptime
> ------- ------ ------- -------- ----------
> ------
> camel-1 Started 0 0 0 2
> minutes
> {code}
> So after start a suspended context, there is still one in context-list. But
> in JMX tree there are two camel-1 context. This mismatch should be addressed.
> Either improve ContextList command or if it's a suspended context, throw a
> RuntimeException and let users resume it other than starting it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
