[jira] Closed: (DERBY-858) ijConnName test output order is non-deterministic.

["Myrna van Lunteren (JIRA)" <ji...@apache.org>]

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

Myrna van Lunteren closed DERBY-858.
------------------------------------

    Fix Version/s: 10.3.3.1
                   10.4.2.1
       Resolution: Fixed

closing again; the error for which I reopened looks the same to me as DERBY-4617.
Marking also closed in 10.3 and 10.4 as I've backported the fix for DERBY-4536.

> ijConnName test output order is non-deterministic.
> --------------------------------------------------
>
>                 Key: DERBY-858
>                 URL: https://issues.apache.org/jira/browse/DERBY-858
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>            Reporter: Daniel John Debrunner
>            Assignee: Myrna van Lunteren
>            Priority: Minor
>             Fix For: 10.3.3.1, 10.4.2.1, 10.5.3.1, 10.6.1.0
>
>         Attachments: DERBY-858.diff, DERBY-858.diff2, DERBY-858_105.diff
>
>
> The test loads four initial connections using these ij.connection properties in the test's _app.properties file.
> ij.connection.connOne=jdbc:derby:wombat;create=true
> ij.connection.connTwo=jdbc:derby:lemming;create=true
> ij.connection.connThree=jdbc:noone:fruitfly;create=true
> ij.connection.connFour=jdbc:derby:nevercreated
> The order these connections are created, and hence the order of the test output is only determined by the hash table ordering of the properties file. Making small changes in  ijConnName_app.properties files can change the order, making the test appear to fail.
> E.g. I tried to enable the test with a security manager by modifying the noSecurityManger to be set to false, and the order changed.

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