[
https://issues.apache.org/jira/browse/CAMEL-12588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16518258#comment-16518258
]
ASF GitHub Bot commented on CAMEL-12588:
----------------------------------------
GitHub user gsudharsan opened a pull request:
https://github.com/apache/camel/pull/2387
CAMEL-12588 AggregateProcessor does not stop AggregateTimeoutChecker
threads on stop call
doStart() starts back timeoutCheckerExecutorService only if it is null
(it does not consider the
state of the pool)
So, I have set timeoutCheckerExecutorService to null in doStop() (like in
doShutDown())
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gsudharsan/camel CAMEL-12588
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/2387.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2387
----
commit 63cce946b4001573d004a584ab26f5a4545e58e1
Author: Sudharsan Govindarajan <sudharsan.govindarajan@...>
Date: 2018-06-20T15:16:56Z
CAMEL-12588 AggregateProcessor does not stop AggregateTimeoutChecker
threads on stop call
----
> AggregateProcessor does not stop AggregateTimeoutChecker threads on stop call
> -----------------------------------------------------------------------------
>
> Key: CAMEL-12588
> URL: https://issues.apache.org/jira/browse/CAMEL-12588
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
> Affects Versions: 2.21.1
> Reporter: Sudharsan Govindarajan
> Assignee: Andrea Cosentino
> Priority: Major
>
> When a Aggregator route is stopped, only the AggregateRecoveryChecker threads
> are stopped and not the AggregateTimeoutChecker threads. They keep lingering
> around.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
