db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-6181) fix AutoloadTest to support running concurrently when different base ports are specified.
Date Wed, 08 May 2013 14:43:16 GMT

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

Myrna van Lunteren updated DERBY-6181:
--------------------------------------

    Attachment: DERBY-6181.diff

Attaching a patch which:

- passes the basePort setting on to any spawned processes using -Dderby.tests.basePort
- starts NetworkServerControl with userid and pwd (as before) and port number (and hostname,
as there's no constructor with just the other 3 params) if basePort property is set
- sets the derby.drda.portNumber property in the JDBCDriversEmbeddedTest, because it uses
derby.drda.startNetworkServer, which otherwise defaults to 1527.
  I think it's OK to make this change as it's not the purpose of this test to test the portnumber
- that's tested in derbynet.DerbyNetAutoStartTest.
- removes the skipping from DERBY-6178 if non-default port is specified.

tests ran cleanly with this change, both suites.All as well jdbcapi._Suite run concurrently.
I plan to commit this later today if there are no comments.
                
> fix AutoloadTest to support running concurrently when different base ports are specified.
> -----------------------------------------------------------------------------------------
>
>                 Key: DERBY-6181
>                 URL: https://issues.apache.org/jira/browse/DERBY-6181
>             Project: Derby
>          Issue Type: Bug
>          Components: Test
>    Affects Versions: 10.9.2.2, 10.10.1.2, 10.11.0.0
>            Reporter: Mike Matrigali
>         Attachments: DERBY-6181.diff
>
>
> This test is currently disabled by DERBY-6178 when a non-default base port is specified.
 It would be nice if it could run
> in the nightly regression runs where multiple suites.all are run using differen base
ports.
> This test currently spawns a new process to test auto loading.  I think the changes necessary
are:
> 1) get the non-default baseport over to the spawned process.  I think you can add a -D
argument to 
>     the spawn command for this.
> 2) change the code that starts a network server to use the new baseport.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message