db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1114) derbynet/testSecMec.java fails intermittently and test exits mysteriously when server is shutdown as part of the testrun.
Date Mon, 20 Mar 2006 19:35:00 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1114?page=all ]

Knut Anders Hatlen updated DERBY-1114:
--------------------------------------

    Attachment: Stdout.java

Bryan wrote:

> That seems to leave the "somebody's closing System.out" theory as
> the most promising.
>
> Now I just have to figure out a way to pursue that theory. I don't
> know how to set a breakpoint on this condition, nor do I know how to
> search for it in the code using find and grep. Hmmm....

Maybe you could create a stream wrapper class which prints a stack
trace in its close method, and set System.out/System.err to an
instance of that class. See the attached file for an example.

> 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, Stdout.java
>
> 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


Mime
View raw message