Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <819013.372711279107889918.JavaMail.jira@thor>
Date: Wed, 14 Jul 2010 07:44:49 -0400 (EDT)
From: "Kristian Waagan (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Updated: (DERBY-4700) Add method to obtain a bogus port in
 TestConfiguration
In-Reply-To: <4169291.1681276583304138.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kristian Waagan updated DERBY-4700:
-----------------------------------

    Attachment: derby-4700-2a-static_bogus.diff

Patch 2a makes the bogus port static, such that it is shared between all TestConfiguration instances in a VM. It also increases the max port count to 11 - we're already using that many ports so the next change that requires another alternative port will trigger the assert in getNextAvailablePort().

Regression tests passed (traditional serial run).
Patch ready for review.
I do plan to commit this fix shortly to stop the tinderbox test from failing. I'll update the wiki page when I commit.

> Add method to obtain a bogus port in TestConfiguration
> ------------------------------------------------------
>
>                 Key: DERBY-4700
>                 URL: https://issues.apache.org/jira/browse/DERBY-4700
>             Project: Derby
>          Issue Type: Improvement
>          Components: Test
>    Affects Versions: 10.7.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Minor
>             Fix For: 10.6.1.1, 10.7.0.0
>
>         Attachments: derby-4700-1a.diff, derby-4700-1b.diff, derby-4700-2a-static_bogus.diff
>
>
> 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.

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