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

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.

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

Ole Solberg updated DERBY-4427:
-------------------------------

    Issue & fix info: [Patch Available]

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

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

Ole Solberg updated DERBY-4427:
-------------------------------

    Attachment: DERBY-existingServer_Fix_stat.txt
                DERBY-existingServer_Fix_diff.txt

suites.All ran ok,
as well as distributed replication tests with master port different from 1527.

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

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

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

Myrna van Lunteren commented on DERBY-4427:
-------------------------------------------

I assume this is a problem with 10.5 also; if/when committed, can it get 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.

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

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

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

Committed DERBY-existingServer_Fix_stat.txt to trunk as revision 830897.

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

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

Ole Solberg updated DERBY-4427:
-------------------------------

     Issue & fix info:   (was: [Patch Available])
    Affects Version/s: 10.5.3.0

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

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

Ole Solberg updated DERBY-4427:
-------------------------------

    Component/s:     (was: Replication)

> 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: 10.5.3.0, 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.

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

Ole Solberg closed DERBY-4427.
------------------------------

    Resolution: Fixed

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

     [ 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: 10.5.3.0)

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

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

Kathey Marsden updated DERBY-4427:
----------------------------------

    Fix Version/s: 10.6.0.0

> 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: 10.6.0.0
>         Environment: All
>            Reporter: Ole Solberg
>            Assignee: Ole Solberg
>            Priority: Minor
>             Fix For: 10.6.0.0
>
>         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.