You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ftpserver-dev@incubator.apache.org by "Magnus Lind (JIRA)" <ji...@apache.org> on 2007/11/20 15:19:42 UTC

[jira] Created: (FTPSERVER-116) OutOfMemoryError when clients disconnect without issuing a QUIT command.

OutOfMemoryError when clients disconnect without issuing a QUIT command.
------------------------------------------------------------------------

                 Key: FTPSERVER-116
                 URL: https://issues.apache.org/jira/browse/FTPSERVER-116
             Project: FtpServer
          Issue Type: Bug
          Components: Core
            Reporter: Magnus Lind


I have done some memory profiling regarding this problem:
The class org.apache.ftpserver.listener.ConnectionManagerImpl stores all connections it ceates in its conList member variable.
Normally the connection is removed from conList when it is closed. However, this is only the case if the client issues a QUIT command before closing the connection.
Connections for clients that don't issue a QUIT command before disconnecting are left in the conList variable and never removed.
As far as I understand, It should be ok to disconnect without issuing a QUIT command.
When enough connections are left in the conList variable the jvm runs out of memory.


-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (FTPSERVER-116) OutOfMemoryError when clients disconnect without issuing a QUIT command.

Posted by "Niklas Gustavsson (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FTPSERVER-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12544060 ] 

Niklas Gustavsson commented on FTPSERVER-116:
---------------------------------------------

Is this using the MINA or IO listener?

> OutOfMemoryError when clients disconnect without issuing a QUIT command.
> ------------------------------------------------------------------------
>
>                 Key: FTPSERVER-116
>                 URL: https://issues.apache.org/jira/browse/FTPSERVER-116
>             Project: FtpServer
>          Issue Type: Bug
>          Components: Core
>            Reporter: Magnus Lind
>
> I have done some memory profiling regarding this problem:
> The class org.apache.ftpserver.listener.ConnectionManagerImpl stores all connections it ceates in its conList member variable.
> Normally the connection is removed from conList when it is closed. However, this is only the case if the client issues a QUIT command before closing the connection.
> Connections for clients that don't issue a QUIT command before disconnecting are left in the conList variable and never removed.
> As far as I understand, It should be ok to disconnect without issuing a QUIT command.
> When enough connections are left in the conList variable the jvm runs out of memory.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Commented: (FTPSERVER-116) OutOfMemoryError when clients disconnect without issuing a QUIT command.

Posted by "Magnus Lind (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FTPSERVER-116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12544191 ] 

Magnus Lind commented on FTPSERVER-116:
---------------------------------------

The default ftpd.properties file is used so it should be the MINA-listener.


> OutOfMemoryError when clients disconnect without issuing a QUIT command.
> ------------------------------------------------------------------------
>
>                 Key: FTPSERVER-116
>                 URL: https://issues.apache.org/jira/browse/FTPSERVER-116
>             Project: FtpServer
>          Issue Type: Bug
>          Components: Core
>            Reporter: Magnus Lind
>
> I have done some memory profiling regarding this problem:
> The class org.apache.ftpserver.listener.ConnectionManagerImpl stores all connections it ceates in its conList member variable.
> Normally the connection is removed from conList when it is closed. However, this is only the case if the client issues a QUIT command before closing the connection.
> Connections for clients that don't issue a QUIT command before disconnecting are left in the conList variable and never removed.
> As far as I understand, It should be ok to disconnect without issuing a QUIT command.
> When enough connections are left in the conList variable the jvm runs out of memory.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.