[
https://issues.apache.org/jira/browse/CAMEL-19759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17756380#comment-17756380
]
Rhuan Rocha commented on CAMEL-19759:
-------------------------------------
Hi [~orpiske]
I noticed that the stack trace is indicating the following line:
org.apache.camel.support.cache.ServicePool.doStop(ServicePool.java:193).
{code:java}
@Override
protected void doStop() throws Exception {
cleanUp();
pool.values().forEach(Pool::stop);
pool.clear();
if (cache != null) {
synchronized (cacheLock) {
cache.values().forEach(ServicePool::stop);
cache.clear();
}
}
singlePoolEvicted.values().forEach(Pool::stop);
singlePoolEvicted.clear();
}
{code}
Checking the code looks like the cleanUp has already cleaned the
singlePoolEvicted map. It looks like lines 192 and 193 are not needed. Am I
correct?
> performance: Camel is hanging up during shutdown
> ------------------------------------------------
>
> Key: CAMEL-19759
> URL: https://issues.apache.org/jira/browse/CAMEL-19759
> Project: Camel
> Issue Type: Bug
> Affects Versions: 3.20.6
> Reporter: Otavio Rodolfo Piske
> Assignee: Otavio Rodolfo Piske
> Priority: Major
> Attachments: dump3.hprof, jstack-3.20.4.txt, jstack.txt
>
>
> Under high load, Camel is taking a very long time to shutdown. The
> investigation points to something happening while the ServicePool is stopping.
> Note: this problem is still under investigation.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
