You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Mike Matrigali (JIRA)" <ji...@apache.org> on 2013/04/15 18:48:15 UTC

[jira] [Created] (DERBY-6181) fix AutoloadTest to support running concurrently when different base ports are specified.

Mike Matrigali created DERBY-6181:
-------------------------------------

             Summary: 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.10.1.2, 10.9.2.2, 10.11.0.0
            Reporter: Mike Matrigali


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