[
https://issues.apache.org/activemq/browse/CAMEL-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60145#action_60145
]
Tarjei Huse commented on CAMEL-2824:
------------------------------------
I can confirm that the deadlock test I created does not fail in multiple runs.
The change has been implemented to the system so we'll see if it works.
> Deadlock in org.apache.camel.util.DefaultTimeoutMap
> ---------------------------------------------------
>
> Key: CAMEL-2824
> URL: https://issues.apache.org/activemq/browse/CAMEL-2824
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-core
> Affects Versions: 2.3.0
> Environment: Centos 4, Java HotSpot(TM) Server VM (11.0-b15 mixed
> mode)
> Reporter: Tarjei Huse
> Assignee: Claus Ibsen
> Fix For: 2.4.0
>
> Attachments: camel-base-context.xml, deadlock.log,
> DeadlockTestCase.java
>
>
> After running a camel route with a camel Aggregator for a while, I get a
> deadlock in org.apache.camel.util.DefaultTimeoutMap. A full processdump is
> attached to this bug.
> I have also tried to recreate this as failing testcase, but without any luck
> so far.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
