Derby
  1. Derby
  2. DERBY-4700

Add method to obtain a bogus port in TestConfiguration

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 10.7.1.1
    • Fix Version/s: 10.6.2.1, 10.7.1.1
    • Component/s: Test
    • Labels:
      None

      Description

      In some cases one needs to obtain a port number on which there is no Derby network server.
      Today this is solved in an ad-hoc way, for instance by using the current port minus one. When running tests in parallel, there is a chance that a port where there actually is a Derby network server listening is picked.

      As a start, I suggest that the bogus port is allocated to the last port in the port range configured for the run: baseport + MAX_PORTS_USED -1.

      1. derby-4700-2a-static_bogus.diff
        4 kB
        Kristian Waagan
      2. derby-4700-1b.diff
        5 kB
        Kristian Waagan
      3. derby-4700-1a.diff
        4 kB
        Kristian Waagan

        Issue Links

          Activity

          No work has yet been logged on this issue.

            People

            • Assignee:
              Kristian Waagan
              Reporter:
              Kristian Waagan
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development