[
https://issues.apache.org/jira/browse/CAMEL-12588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16518257#comment-16518257
]
ASF GitHub Bot commented on CAMEL-12588:
----------------------------------------
gsudharsan opened a new pull request #2387: CAMEL-12588 AggregateProcessor does
not stop AggregateTimeoutChecker
URL: https://github.com/apache/camel/pull/2387
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())
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> 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)
