Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
10.9.2.2, 10.10.2.0, 10.11.1.1
-
High Value Fix
-
Regression Test Failure
Description
IBM lab nightly regression testing is seeing numerious intermittent errors while running the
AutoloadTest. This regression testing often runs multiple runs of Suites.all on the same machine at
the same time and uses the -Dderby.tests.basePort=3500 option to the tests to insure network
server is created on different ports and don't intefere.
I think the following code in this test that spawn a process is not going pass that port info onto the network
server startup and then lead to problems:
/**
- Run
{@code AutoloadTest}
in a separate JVM.
{ "junit.textui.TestRunner", spawnedTestClass.getName() }
*/
public void spawnProcess() throws Exception {
String[] cmd =;
SpawnedProcess proc =
new SpawnedProcess(execJavaCmd(cmd), spawnedTestClass.getName());
if (proc.complete() != 0)
{ fail(proc.getFailMessage("Test process failed")); }}
Attachments
Attachments
Issue Links
- is duplicated by
-
DERBY-5800 test failure in AutoloadTest; AssertionFailedError: Test process failed:Spawned caused by SQLNonTransientConnectionException - Software caused connection abort: recv failed.
- Closed
-
DERBY-5932 testAutoNetworkServerBoot fails with Invalid authentication
- Closed
-
DERBY-6170 testSuccessfulConnect failure on trunk(revision 1465166) with ibm 16
- Closed
-
DERBY-3861 'testAutoNetworkServerBoot' fails with 'Network Server state incorrect expected:<false> but was:<true>'
- Closed
- is related to
-
DERBY-5664 Include driver tests in jdbcapi suite
- Closed
- relates to
-
DERBY-6181 fix AutoloadTest to support running concurrently when different base ports are specified.
- Closed