[DERBY-5518] NetworkServerMBeanTest timed out waiting for network server to start

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 10.9.1.0
• Component/s: Test
• Bug behavior facts: Regression Test Failure
• Assignee: Unassigned
• Reporter: Knut Anders Hatlen
• Created: 02/Dec/11 18:12
• Updated: 24/Jul/12 17:26
• Resolved: 06/Dec/11 10:34

Description

There was 1 failure:
1) NetworkServerMBeanTest:clientjunit.framework.AssertionFailedError: Timed out waiting for network server to start:Spawned SpawnedNetworkServer exitCode=143
at org.apache.derbyTesting.junit.NetworkServerTestSetup.setUp(NetworkServerTestSetup.java:205)
at junit.extensions.TestSetup$1.protect(TestSetup.java:20)
at junit.extensions.TestSetup.run(TestSetup.java:25)
at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
at junit.extensions.TestSetup.run(TestSetup.java:25)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:21)
at junit.extensions.TestSetup.run(TestSetup.java:25)

Might be the same problem as seen in DERBY-4201, DERBY-4265, DERBY-4914, DERBY-5194.

Issue Links

• duplicates: DERBY-4201 SecureServerTest AssertionFailedError: Timed out waiting for network server to start
• is related to: DERBY-5123 address a select number of intermittent test issues - goal is to get all nightly tests at trunk running clean for at least 2 weeks
• relates to: DERBY-4265 timed out waiting for server to start in StatementPoolingTest
• relates to: DERBY-5194 AutoloadTest timed out waiting for network server to start
• relates to: DERBY-4201 SecureServerTest AssertionFailedError: Timed out waiting for network server to start
• relates to: DERBY-4914 Utf8CcsidManagerClientTest timed out waiting for network server to start