[
https://issues.apache.org/jira/browse/SSHD-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16493425#comment-16493425
]
Goldstein Lyor commented on SSHD-340:
-------------------------------------
That would be a great help - in any case, the SSH server is intended to work as
a "server" - i.e., stopping it means exiting the application. Multiple restarts
of the same server or even stopping it, creating a new instance and starting
the new instance may leave "stale" threads/settings/etc... We did not design
for this mode of usage, though we have made efforts to clean-up when server (or
client...) are {{stop}}-ed - as per your description probably not enough.
> Hanging threads
> ---------------
>
> 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)
