db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bryan Pendleton (JIRA)" <derby-...@db.apache.org>
Subject [jira] Resolved: (DERBY-1114) derbynet/testSecMec.java fails intermittently and test exits mysteriously when server is shutdown as part of the testrun.
Date Fri, 24 Mar 2006 17:10:25 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1114?page=all ]
     
Bryan Pendleton resolved DERBY-1114:
------------------------------------

    Resolution: Won't Fix

Sunitha, I have satisfied myself that I was encountering a JVM bug here, *not* a Derby bug.

Specifically, I believe I was encountering this bug:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4927336

Although that bug report seems to indicate that this bug was present only in JDK 1.5 betas,
I believe that it was also present in some versions of JDK 1.4.2. This belief is based primarily
on some of the comments in the bug report page, and also in this web page:
http://forum.java.sun.com/thread.jspa?threadID=563298&messageID=3575166

I am able to reproduce the problem with JDK 1.4.2_06, which is mentioned in the above web
pages as being one of the releases afflicted with this problem.

I tried running with both 1.5.0_05, and with 1.4.2_11. In both cases, I can *not* reproduce
the bug.

Since switching to a different JVM definitely resolves the behavior for me, and since the
bug report seems to match my symptoms closely (I have even seen the "Real-time signal 28"
message a few times), I believe that there's enough evidence here to conclusively resolve
this bug as being a JVM bug, not a Derby problem.

If you're comfortable with that resolution, could you please mark this bug closed?

thanks,

bryan


> 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
>     Assignee: Bryan Pendleton
>     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