[DERBY-4238] JMX test failure starting network server doesn't seem to get recorded to the fail directory

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 10.6.1.0
• Component/s: Test
• Labels: derby_triage10_8
• Urgency: Normal
• Assignee: Unassigned
• Reporter: Katherine Marsden
• Created: 19/May/09 23:35
• Updated: 15/Apr/11 09:28

Description

I did a test run and saw this failure:
2) JMXTest:clientjunit.framework.AssertionFailedError: Timed out waiting for network server to start:Spawned SpawnedNetworkServer exitCode=1
at org.apache.derbyTesting.junit.NetworkServerTestSetup.setUp(NetworkServerTestSetup.java:200)
at junit.extensions.TestSetup$1.protect(TestSetup.java:18)
at junit.extensions.TestSetup.run(TestSetup.java:16)
at org.apache.derbyTesting.junit.BaseTestSetup.run(BaseTestSetup.java:57)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:16)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:22)
at junit.extensions.TestSetup$1.protect(TestSetup.java:19)
at junit.extensions.TestSetup.run(TestSetup.java:16)

But there was no directory under the fail directory for this test. I am not sure if the problem is just that it failed to early in the process or if there is something specific about the JMX tests that they don't get recorded to the fail directory.

Issue Links

• is related to: DERBY-5192 Setting up network server for management tests hangs intermittently