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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.9.2.2, 10.10.2.0, 10.11.1.1
• Fix Version/s: 10.9.2.2, 10.10.2.0, 10.11.1.1
• Component/s: Test
• Issue & fix info: High Value Fix
• Bug behavior facts: Regression Test Failure
• Assignee: Myrna van Lunteren
• Reporter: Mike Matrigali
• Created: 15/Apr/13 20:48
• Updated: 16/Apr/14 06:41
• Resolved: 12/May/13 19:12

Description

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.

Issue Links

• is related to: DERBY-6178 AutoloadTest does not proprogate original jvm -D flags to spawned JVM, leading to LAB regression test failures