| Issue 221: | Deadlock in SSHD causes server to be non-responsive | |
| Back to list |
Reported by Shawn Pearce <sop@google.com> on Mon Jun 15 22:59:07 PDT 2009 Source: JIRA GERRIT-222 Affected Version: 2.0 There is a known deadlock in the MINA SSHD which can cause the SSHD to (eventually) become non-responsive to clients, as the various NIO threads deadlock and are unable to continue. The symptom is often seen where a client can't make any progress updating a project, but another client can read it just fine. This appears to occur due to random assignment of new client to NIO processor thread, if the assignment goes to a deadlocked thread, the client become stuck. https://issues.apache.org/jira/browse/SSHD-28 is tracking the upstream issue, and has a potential fix.
Sep 24, 2009
#1
code-rev...@gtempaccount.com
Sep 24, 2009
Update by Shawn Pearce <sop@google.com> on Wed Jul 01 15:56:23 PDT 2009 Fixed in version 2.0.15.
Sep 24, 2009
Update by Shawn Pearce <sop@google.com> on Wed Jul 01 15:56:28 PDT 2009
Sep 24, 2009
Comment by Shawn Pearce <sop@google.com> on Wed Jul 29 08:54:38 PDT 2009 Fixed by https://review.source.android.com/10783 (MINA SSHD r798139)
Sep 24, 2009
Update by Shawn Pearce <sop@google.com> on Wed Jul 29 08:54:38 PDT 2009 Fixed in version 2.0.18.
Status:
Fixed
Sep 25, 2009
(No comment was entered for this change.)
Labels:
FixedIn-2.0.18
Oct 25, 2012
(No comment was entered for this change.)
Status:
Released
|
|
| ► Sign in to add a comment |