mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Goldstein Lyor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SSHD-908) Leak of process handles caused by local port forwarding connections
Date Tue, 19 Mar 2019 00:34:00 GMT

    [ https://issues.apache.org/jira/browse/SSHD-908?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16795516#comment-16795516
] 

Goldstein Lyor commented on SSHD-908:
-------------------------------------

I notice that the issue is referring to version 2,1 - can you try the latest release ? We
have made some improvements to the port forwarding code specifically, While not specifically
targeting leaks, these changes are also part of some stricter resources management where we
allocate late and release early

> Leak of process handles caused by local port forwarding connections
> -------------------------------------------------------------------
>
>                 Key: SSHD-908
>                 URL: https://issues.apache.org/jira/browse/SSHD-908
>             Project: MINA SSHD
>          Issue Type: Bug
>    Affects Versions: 2.1.0
>            Reporter: Roberto Deandrea
>            Priority: Major
>
> Hi,
> We have build an Apache SSHD Client (based on Apache SSHD 2.1.0) to forward local sockets
to target servers.
> Our client is configured to use NIO2 builtin service provider, NIO2 Mina service provider
and NIO2 Netty service provider.
> We have detected a leak of handles monitoring the java process with ALL above NIO2 service
provider.
> When the limit of handles per process is reached, the java process become unresponsive.
>  
> We suspect that the problem could be into Apache SSHD Client code.
> The problem is reproducible in our lab environment.
>  
> Can you help us troubleshoot this problem and in that case what kind of info you need
?
> Did you see a similar problem before and if so, can you give us a solution ?
>  
> Kind Regards
> Roberto Deandrea
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message