[jira] Commented: (DERBY-4427) TestConfiguration.existingServerSuite(....,portNumber) must use the supplied portNumber

["Knut Anders Hatlen (JIRA)" <ji...@apache.org>]

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

Knut Anders Hatlen commented on DERBY-4427:
-------------------------------------------

Hi Ole,
The fix looks good. +1

> 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.