FtpServer
  1. FtpServer
  2. FTPSERVER-360

When no passive ports are available error out immediately rather than waiting for a port to become available

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 1.0.4
    • Fix Version/s: 1.0.7, 1.1.0
    • Component/s: None
    • Labels:
      None

      Description

      Based on the filed issue, http://issues.apache.org/jira/browse/FTPSERVER-359, we probably want to quick fix the code to error out right away when no passive port is available.

      1. FTPSERVER-360.patch
        2 kB
        Sai Pullabhotla

        Activity

        Hide
        Sai Pullabhotla added a comment -

        I think this was already fixed. Can this be closed?

        Show
        Sai Pullabhotla added a comment - I think this was already fixed. Can this be closed?
        Hide
        Niklas Gustavsson added a comment -

        I think this should go in trunk and 1.0.x (to fix the bug reported in 1.0.x).

        I've fixed the forgotten move from branches to tags. My bad.

        Show
        Niklas Gustavsson added a comment - I think this should go in trunk and 1.0.x (to fix the bug reported in 1.0.x). I've fixed the forgotten move from branches to tags. My bad.
        Hide
        Sai Pullabhotla added a comment -

        Okay, I think I got a test case for this. What all branches do you want this fix to go in, in addition to the trunk?

        A side note - I do see two branches - 1.0.4 and 1.0.x. However, I do not see a 1.0.4 tag. Did we create a branch for 1.0.4 where it should have been a tag?

        Show
        Sai Pullabhotla added a comment - Okay, I think I got a test case for this. What all branches do you want this fix to go in, in addition to the trunk? A side note - I do see two branches - 1.0.4 and 1.0.x. However, I do not see a 1.0.4 tag. Did we create a branch for 1.0.4 where it should have been a tag?
        Hide
        Niklas Gustavsson added a comment -

        Yeah, that's right.

        Show
        Niklas Gustavsson added a comment - Yeah, that's right.
        Hide
        Sai Pullabhotla added a comment -

        Niklas,

        Are you looking for a "client" test case, to actually connect to the server and try opening passive connections? Otherwise, the current test cases are good enough.

        Show
        Sai Pullabhotla added a comment - Niklas, Are you looking for a "client" test case, to actually connect to the server and try opening passive connections? Otherwise, the current test cases are good enough.
        Hide
        Niklas Gustavsson added a comment -

        Patche seems good, we also need a test case to show that we now return an error if the passive ports are used.

        Show
        Niklas Gustavsson added a comment - Patche seems good, we also need a test case to show that we now return an error if the passive ports are used.
        Hide
        Sai Pullabhotla added a comment -

        Here is a patch to try out to see if the server locks up as reported in the issue 359. This patch error out immediately when no passive ports are available. This is mainly for testing with the test case provided the submitter of FTPSERVER-359. Not sure if it is ready to be included in the code base.

        Show
        Sai Pullabhotla added a comment - Here is a patch to try out to see if the server locks up as reported in the issue 359. This patch error out immediately when no passive ports are available. This is mainly for testing with the test case provided the submitter of FTPSERVER-359 . Not sure if it is ready to be included in the code base.

          People

          • Assignee:
            Sai Pullabhotla
            Reporter:
            Sai Pullabhotla
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:

              Development