Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <306114527.1142386016910.JavaMail.jira@ajax>
Date: Wed, 15 Mar 2006 01:26:56 +0000 (GMT)
From: "Sunitha Kambhampati (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_12370445 ] 

Sunitha Kambhampati commented on DERBY-1114:
--------------------------------------------

Thanks Bryan for trying out the patch.  If the problem lies in the networkserver.shutdown and the test change to remove the switching of streams doesnt help,  then I guess  there isnt much point  checking in this test change.  So lets just ignore the (Derby1114.diff.txt) patch. 

I thought it was interesting that the shutdown message for server doesnt get to the derby.log for the run where the test exits.   In the network server shutdown method (NetworkServerControlImpl.shutdown), the message would be written to the cloudscapeLogWriter. ( goes to consoleWriter method). If you follow that path, it leads to the Monitor.getStream() and there is a comment there that if streams cannot be setup for some reason, it would default to System.err.   From a quick look, I think if the stream is setup as System.err it doesnot close the stream. 

I can only think of  putting old fashioned println statements in networkserver.shutdown to see what maybe happening.   

Thanks,
Sunitha.

> 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