db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <derby-...@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.
Date Tue, 15 Aug 2006 11:35:18 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1114?page=comments#action_12428101 ] 
Kathey Marsden commented on DERBY-1114:

With all jvms I have tried and for quite a while I have seen this failure on  my machine with
Windows XP.  I think it actually started when I upgraded my machine to Windows XP from Windows
2000, but I am not totally sure of that.  It occurs with both classes and jars, with both
derby client and jcc  and is not intermittent.  The test fails every time.

I am attaching  the test output (testSecMec_test_output.zip)  to confirm that it is the same
thing, but it sure seems like it because as Sunitha indicated the derby.log only shows  two
shutdown messages, instead of four.

The JVM for this run is:

 java -version
ava version "1.5.0"
ava(TM) 2 Runtime Environment, Standard Edition (build pwi32dev-20060511 (SR2))
BM J9 VM (build 2.3, J2RE 1.5.0 IBM J9 2.3 Windows XP x86-32 j9vmwi3223-20060504 (JIT enabled)
9VM - 20060501_06428_lHdSMR
IT  - 20060428_1800_r8
C   - 20060501_AA)
CL  - 20060511a

OS is Windows XP Professional version 2002 Service Pack 2

All Sun and IBM jdk's that I have tried on this machine have the same failure,  I am retiring
this machine so thought I would record these results in case someone else hit the issue. Sadly,
 I don't have a solution to offer.  One thing I tried, because I know it has caused other
issues in the past was switching the test to just use port 1527 instead of 20000. That made
no difference.

When I set up my new machine I will see if I have the same problem.  

> 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
>          Issue Type: Bug
>          Components: Network Server, Test
>    Affects Versions:
>         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
>         Assigned To: 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


View raw message