[
https://issues.apache.org/jira/browse/SSHD-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16553394#comment-16553394
]
Jared Wiltshire edited comment on SSHD-340 at 7/29/18 7:44 PM:
---------------------------------------------------------------
I've definitely seen the issue with the server threads not stopping correctly
in version -1.0.0- 2.0.0
I've also just discovered that you can't stop an instance of SshServer then
restart it again safely. This is due to the AbstractCloseable superclass which
never has its state set back to State.Opened when you start it again. This
means if you start SshServer after stopping, it starts back up OK but you can
never stop it again.
was (Author: jaredwiltshire):
I've definitely seen the issue with the server threads not stopping correctly
in version 1.0.0
I've also just discovered that you can't stop an instance of SshServer then
restart it again safely. This is due to the AbstractCloseable superclass which
never has its state set back to State.Opened when you start it again. This
means if you start SshServer after stopping, it starts back up OK but you can
never stop it again.
> Hanging threads left working when server is shut down
> -----------------------------------------------------
>
> Key: SSHD-340
> URL: https://issues.apache.org/jira/browse/SSHD-340
> Project: MINA SSHD
> Issue Type: Bug
> Affects Versions: 0.12.0
> Reporter: Sampo Savolainen
> Priority: Major
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> SSHD fails to stop properly due to errant threads. I've attached a thread
> dump from a point of execution where everything should have been cleaned up.
> The hanging threads happen only if the server has accepted connections and
> they do not hang forever, they seem to stop themselves after a minute or so.
> This might be an executor pool which is not shut down correctly.
> Earlier versions (0.8.0 and 0.9.0) did not exhibit this behavior.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
