Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <1880435704.1142485742242.JavaMail.jira@ajax>
Date: Thu, 16 Mar 2006 05:09:02 +0000 (GMT)
From: "Bryan Pendleton (JIRA)" <derby-dev@db.apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-1114) derbynet/testSecMec.java fails
 intermittently and test exits mysteriously when server is shutdown as part
 of the testrun.
In-Reply-To: <29629678.1142368001988.JavaMail.jira@ajax>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/DERBY-1114?page=comments#action_12370643 ] 

Bryan Pendleton commented on DERBY-1114:
----------------------------------------

I've been fiddling around with the main loop in testSecMec.java. This loop iterates through various security mechanisms. For each security mechanism, the loop starts up the Network Server with that mechanism, runs various tests, then shuts it down.

My findings so far are interesting:
- Re-ordering all the security mechanisms in the loop didn't affect the bug, So it doesn't seem to have to do with the security mechanism that is used.
- In fact, I altered testSecMec.java so that it just looped 6 times with no security mechanism at all, and the bug still occurred.
- Lastly, and most interestingly, when the bug occurs, it *always* happens after the second time through the loop. Never in dozens of reproduced cases has it ever happened after the 3rd or 4th or 5th time through the loop, nor after the first time.

It seems that if the bug is going to happen in my environment, it always happens after the second time through the loop.


> 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
>         Type: Bug
>   Components: Network Server, Test
>     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
>     Priority: Minor
>  Attachments: Derby1114.diff.txt
>
> 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