db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ole Solberg (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4427) TestConfiguration.existingServerSuite(....,portNumber) must use the supplied portNumber
Date Tue, 03 Nov 2009 09:27:59 GMT

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

Ole Solberg updated DERBY-4427:

    Affects Version/s:     (was:

The problem was not in 10.5.
10.5 had the original correct use of the supplied portNumber parameter.

> 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: Test
>    Affects Versions:
>         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.

View raw message