[DERBY-1114] derbynet/testSecMec.java fails intermittently and test exits mysteriously when server is shutdown as part of the testrun.

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Duplicate
• Affects Version/s: 10.2.1.6
• Component/s: Network Server, Test
• 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
• Assignee: Unassigned
• Reporter: Sunitha Kambhampati
• Created: 15/Mar/06 04:25
• Updated: 28/May/07 03:17
• Resolved: 28/May/07 03:17

Description

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.

Issue Links

• relates to: DERBY-1751 derbynet/testSecMec.java fails with ShutdownException in DerbyNetClient framework