Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <307428638.1256814899370.JavaMail.jira@brutus>
Date: Thu, 29 Oct 2009 11:14:59 +0000 (UTC)
From: "Ole Solberg (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-4427)
 TestConfiguration.existingServerSuite(....,portNumber) must use the
 supplied portNumber
In-Reply-To: <267702419.1256735939600.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-4427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12771386#action_12771386 ] 

Ole Solberg commented on DERBY-4427:
------------------------------------

Yes, for completeness, it should be backported.


> TestConfiguration.existingServerSuite(....,portNumber) must use the supplied portNumber
> ---------------------------------------------------------------------------------------
>
>                 Key: DERBY-4427
>                 URL: https://issues.apache.org/jira/browse/DERBY-4427
>             Project: Derby
>          Issue Type: Bug
>          Components: Replication, Test
>    Affects Versions: 10.6.0.0
>         Environment: All
>            Reporter: Ole Solberg
>            Assignee: Ole Solberg
>            Priority: Minor
>         Attachments: DERBY-existingServer_Fix_diff.txt, DERBY-existingServer_Fix_stat.txt
>
>
> When testing distributed replication I found that test clients/load would always use (default) port 1527 even if a different master port number had been specified. The correct/specified port number was used when starting the master server. 
> This was caused by a call to 'TestConfiguration.getCurrent().getPort()' on an uninitialized TestConfiguration. The fix is to use the supplied portNumber parameter.

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