You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "simon trudeau (JIRA)" <ji...@apache.org> on 2008/06/06 17:13:45 UTC
[jira] Created: (DIRMINA-604) Deadlock occurs when implementing two
mina StateMachine
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
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!)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRMINA-604) Deadlock occurs when implementing two
mina StateMachine
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRMINA-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRMINA-604:
--------------------------------------
Fix Version/s: (was: 2.0.0-M4)
2.0.0-RC1
> 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.0-RC1
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRMINA-604) Deadlock occurs when implementing two
mina StateMachine
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRMINA-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRMINA-604:
--------------------------------------
Fix Version/s: (was: 2.0.0-RC1)
3.0.0-M1
Postoned to the next version.
Having those StateMachine mechanism available is cool, but if nobody can maintain it, at some point, we will have to move it to the sandbox.
> 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: 3.0.0-M1
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRMINA-604) Deadlock occurs when implementing two
mina StateMachine
Posted by "simon trudeau (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRMINA-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
simon trudeau updated DIRMINA-604:
----------------------------------
Description:
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.
was:
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!)
> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRMINA-604) Deadlock occurs when implementing two
mina StateMachine
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRMINA-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRMINA-604:
--------------------------------------
Fix Version/s: 2.0.0-M4
It would be cool if this could be fixed in 2.0
> 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.0-M4
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.