[
http://issues.apache.org/jira/browse/DERBY-1114?page=comments#action_12428159 ]
Daniel John Debrunner commented on DERBY-1114:
----------------------------------------------
The failure I'm seeing is due to this code: line 241
// Wait for the NetworkServer to start.
if (!isServerStarted(networkServer, 60))
System.exit(-1);
The test should not call System.exit(). Instead it should print a failure
message and then break to end the test.
More like.
// Wait for the NetworkServer to start.
if (!isServerStarted(networkServer, 60)) {
System.out.println("FAIL: Server failed to respond
to ping - ending test");
break;
}
The test continued to fail for me, with the above error, but if I increased the
loop count for isServerStarted to 120 from 60 it seems to pass every time.
> derbynet/testSecMec.java fails intermittently and test exits mysteriously
> when server is shutdown as part of the testrun.
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1114
> URL: http://issues.apache.org/jira/browse/DERBY-1114
> Project: Derby
> Issue Type: Bug
> Components: Network Server, Test
> Affects Versions: 10.2.0.0
> Environment: Java Version: 1.4.2_06
> Java Vendor: Sun Microsystems Inc.
> Java home: /usr/local/lib/j2sdk1.4.2_06/jre
> OS name: Linux
> OS architecture: i386
> OS version: 2.4.21-27.0.2.ELsmp
> Reporter: Sunitha Kambhampati
> Assigned To: Bryan Pendleton
> Priority: Minor
> Attachments: Derby1114.diff.txt, Stdout.java,
> testSecMec_test_output.zip
>
>
> The test derbynet/testSecMec.java fails intermittently in a strange way that
> the test actually exits before finishing the full test.
> This issue was noticed by Bryan when he ran derbyall with the derby-1080 fix.
> Some discussion and analysis that has been done is in Derby-1080. Please read
> comments in DERBY-1080. Some main links in
> http://issues.apache.org/jira/browse/DERBY-1080#action_12370260
> http://issues.apache.org/jira/browse/DERBY-1080#action_12370374
> In short: the test does some switching of System.out and System.err streams
> before calling networkserver.shutdown. This code was added to this test as
> part of fix for derby-273. for some reason, the networkserver.shutdown call
> makes the test to exit. One theory is that the network server.shutdown is
> causing the standard out streams to close and thus the test exits.
> -- Need to investigate what is the cause for this intermittent failure and
> how/why networkserver.shutdown is closing the stream or making the test to
> exit prematurely.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
