mina-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Latorre (JIRA)" <j...@apache.org>
Subject [jira] Closed: (FTPSERVER-303) Passive data connection stuck in CLOSE_WAIT.
Date Mon, 25 May 2009 07:54:45 GMT

     [ https://issues.apache.org/jira/browse/FTPSERVER-303?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

David Latorre closed FTPSERVER-303.

       Resolution: Fixed
    Fix Version/s: 1.0.0

Committed to 1.0.0, 1.0.1 and trunk. I'm sorry for the delay!

Alberto, can you  proceed to test the fix and see if it's solving your problem? In my tests
the connections are immediately closed  so you should expect no issues here though. 

> Passive data connection stuck in CLOSE_WAIT.
> --------------------------------------------
>                 Key: FTPSERVER-303
>                 URL: https://issues.apache.org/jira/browse/FTPSERVER-303
>             Project: FtpServer
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.0.0, 1.0.1
>            Reporter: Alberto Vazquez
>            Assignee: David Latorre
>             Fix For: 1.0.2, 1.0.1, 1.0.0
> We are using a  week old snapshot  from Ftpserver (it seems  a bit newer than the 1.0.1
freeze). One of our clients reported that  the data connection was being kept open  for a
 long time ...  They are using a propietary client its name I cannot remember and  it was
an SSL data connection in passive mode.
> After checking this using a windows Filezilla client   and a Linux server running ftpserver
(on top of Sun Java Application Server 9) we noticed that the FTP Server had several sockets
in  CLOSE_WAIT state. At the client side, the state was FIN_WAIT_2.
> To my mind , this could be related with the Socket leaking bug  that was previously reported
with SSL passive connections or its workaround although it might be SJAS fault or-who-knows.
Since we don't have a  linux machine available for testing I don't know what the real problem

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

View raw message