[jira] [Updated] (DIRMINA-604) Deadlock occurs when implementing two mina StateMachine

["Julien Vermillard (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DIRMINA-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julien Vermillard updated DIRMINA-604:
--------------------------------------

    Fix Version/s:     (was: 3.0.0-M1)
                   2.0.6

> Deadlock occurs when implementing two mina StateMachine 
> --------------------------------------------------------
>
>                 Key: DIRMINA-604
>                 URL: https://issues.apache.org/jira/browse/DIRMINA-604
>             Project: MINA
>          Issue Type: Bug
>          Components: Statemachine
>    Affects Versions: 2.0.0-M2
>         Environment: Bug found under:
>  - windows vista business edition 
> - dual core intel machine 
> - jdk6_update6 
>            Reporter: simon trudeau
>            Priority: Critical
>             Fix For: 2.0.6
>
>
> For mailing list discussion on the issue, see:
> http://mina.markmail.org/message/hp2bkg56sf5f6l56?q=list:org.apache.mina.users&page=1#query:list%3Aorg.apache.mina.users+page:1+mid:l6up4s36uag6yvll+state:results
> With the mailing list thread is included a jstack stack trace to illustrate the deadlock.
> A deadlock occurs when a Mina StateMachine's Filter (A) reads data using messageReceived()  while another mina StateMachine's Filter (B) write data at the same time using filterWrite().
> My current oberservation show that what witch I thought only occured rarely happens in fact very frequently when there are few concurrent connections! (Basically the faster we can get a response to a request, the more likely the chance of this situation happening!) 
> The effect of such a deadlock is that it freezes the whole application without possibility of recovering.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira