[prev in list] [next in list] [prev in thread] [next in thread]
List: mina-dev
Subject: [jira] Commented: (DIRMINA-737) StateMachine deadlock on
From: "Julien Vermillard (JIRA)" <jira () apache ! org>
Date: 2009-08-25 15:24:02
Message-ID: 119510629.1251213842209.JavaMail.jira () brutus
[Download RAW message or body]
[ https://issues.apache.org/jira/browse/DIRMINA-737?page=com.atlassian.jira.plugin \
.system.issuetabpanels:comment-tabpanel&focusedCommentId=12747459#action_12747459 ]
Julien Vermillard commented on DIRMINA-737:
-------------------------------------------
Niklas (Therning) any idea ? There is some strange deadlock managing code there, but \
it's looking inneficent.
> StateMachine deadlock on StateContext synchronization
> -----------------------------------------------------
>
> Key: DIRMINA-737
> URL: https://issues.apache.org/jira/browse/DIRMINA-737
> Project: MINA
> Issue Type: Bug
> Components: Statemachine
> Affects Versions: 2.0.0-M6
> Environment: Mac OSX 10.5.8
> JDK 1.5.0_19-137
> Reporter: Rafael Marins
> Attachments: deadlockDump.txt
>
>
> I've found a deadlock at StateMachine#handle(StateMachine.java:129) and \
> StateMachineProxyBuilder \
> $MethodInvocationHandler.invoke(StateMachineProxyBuilder.java:253), when using two \
> layered state machines in pipeline. It get into deadlock because both methods seems \
> to be called concurrently.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic