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] Created: (DERBY-4427) TestConfiguration.existingServerSuite(....,portNumber) must use the supplied portNumber
Date Wed, 28 Oct 2009 13:18:59 GMT
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


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.


Mime
View raw message