[
https://issues.apache.org/jira/browse/FTPSERVER-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niklas Gustavsson closed FTPSERVER-137.
---------------------------------------
Resolution: Fixed
Fixed by caching the remote address that would otherwise be reset after the
socket is closed due to the SSL exception.
> Concurrent connections count not decreased on SSL socket close
> --------------------------------------------------------------
>
> Key: FTPSERVER-137
> URL: https://issues.apache.org/jira/browse/FTPSERVER-137
> Project: FtpServer
> Issue Type: Bug
> Components: Core
> Affects Versions: 1.0-M1
> Reporter: Niklas Gustavsson
> Assignee: Niklas Gustavsson
> Fix For: 1.0-M2
>
>
> Reported by Jeroen Cranendonk
> "I'm trying to setup a ftps server using the latest svn checkout (As in today
> :) ).
> Things work fine, except when a ftp client (FileZilla in my case) disconnects.
> Underneath is a log showing the error/warning that I get on disconnect (using
> the disconnect button on filezilla, which I think is a pretty well accepted
> way on closing the connection).
> When using flashfxp I seem the same thing happening, even when it first sends
> a QUIT (added a log for that after the filezilla one, hope the long mail
> isn't a problem! :) ).
> Now this warning isn't such a big issue, but it seems the 'logout' code isn't
> called when this happens.
> The result of this is that I run out of logins, for example with 3 'anonymous
> logins' (which = 3 simultaneous logins),
> I will not be able to log in anymore after three -sequential- logins. And
> it's not hanging connections, even if I close the client entirely, and try to
> reconnect, I still get 'Response: 421 Maximum login limit has been
> reached.'
> I've even checked with the tcp view tool from sysinternals that there's
> really no connections left.
> So I think that because of the thrown exception, the code that normally
> decreases the login count isn't called, my guess anyways.
> Can someone please verify if this is a bug (and possibly fix it? or tell me
> how to fix it ;) )."
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
