You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2010/06/18 07:37:52 UTC
[jira] Resolved: (CAMEL-2824) Deadlock in
org.apache.camel.util.DefaultTimeoutMap
[ https://issues.apache.org/activemq/browse/CAMEL-2824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-2824.
--------------------------------
Assignee: Claus Ibsen
Fix Version/s: 2.4.0
Resolution: Fixed
trunk: 955841.
Tarjei thanks for the dump and reporting this issue.
I have committed a fix. Can you test it on your system with the fix?
> 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.