[
https://issues.apache.org/jira/browse/CAMEL-8499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14366727#comment-14366727
]
Claus Ibsen commented on CAMEL-8499:
------------------------------------
The idea of having state of the shutdown task is a good idea.
Notice the shutdown is also used for shutting down routes, not only camel
itself. So the state needs to know if its for a route or for camel context
itself.
> Graceful shutdown - Add kill operation
> --------------------------------------
>
> Key: CAMEL-8499
> URL: https://issues.apache.org/jira/browse/CAMEL-8499
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, jmx
> Affects Versions: 2.15.0
> Reporter: Claus Ibsen
> Priority: Minor
> Fix For: Future
>
>
> When Camel is doing a graceful shutdown, it may take some time to shutdown to
> drain inflight exchanges. And as that by default has a timeout of 300 seconds
> that is counting down. Then sometimes end users dont bother, eg its a test
> environment etc. Then we should have a JMX / Java API on graceful shutdown to
> terminate this timeout asap. Its basically to cancel the future task to do it.
> We can then also have a karaf commands as well. Maybe its reusing the stop
> command but with a --kill flag.
> If kill is a too extreme wording, we could use force stop or something
> instead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
