[
https://issues.apache.org/jira/browse/CAMEL-12588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16518261#comment-16518261
]
Sudharsan Govindarajan commented on CAMEL-12588:
------------------------------------------------
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()) and made a new PR [https://github.com/apache/camel/pull/2387]
I have tested this a bit more thorough than the previous times. Both the
recovery checker and timeout checker threads now stop and start as per the
method calls. Sorry about the previous oversight
> 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)
