Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-4700

Add method to obtain a bogus port in TestConfiguration

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 10.7.1.1
    • 10.6.2.1, 10.7.1.1
    • Test
    • 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.

      Attachments

        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

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            kristwaa Kristian Waagan
            kristwaa Kristian Waagan
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment