db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "A B (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1912) derbynet/ShutDownDBWhenNSShutsDownTest.junit fails with ibm131, hangs with jdk131
Date Tue, 03 Oct 2006 17:33:25 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1912?page=comments#action_12439570 ] 
            
A B commented on DERBY-1912:
----------------------------

It was mentioned on the derby-dev list that we are no longer claiming support for 1.3 jvms
with Derby 10.3 and higher (thanks Myrna!).  I have confirmed that the test runs without error
against the latest 10.2 codeline and also with the 10.2.1.6 release candidate.

So the question now becomes: do we need to disable the test so that it doesn't run against
1.3 JVMs, or do we just  ignore the failure and assume that people will stop running their
10.3 tests with 1.3 JVMs?

> derbynet/ShutDownDBWhenNSShutsDownTest.junit fails with ibm131, hangs with jdk131
> ---------------------------------------------------------------------------------
>
>                 Key: DERBY-1912
>                 URL: http://issues.apache.org/jira/browse/DERBY-1912
>             Project: Derby
>          Issue Type: Test
>          Components: Regression Test Failure
>    Affects Versions: 10.3.0.0
>         Environment: Network client test with ibm131 or  Sun jdk131
>            Reporter: A B
>            Priority: Minor
>
> derbynet/ShutDownDBWhenNSShutsDownTest.junit fails with ibm131 with the following error:
> > ..E
> > There was 1 error:
> > 1) testEngineShutdownDoesNotTakeDownNS(org.apache.derbyTesting.functionTests.tests.derbynet.ShutDownDBWhenNSShutsDownTest)java.sql.SQLException:
java.net.ConnectException : Error connecting to server xxxFILTERED_HOSTNAMExxx on port 1527
with message Connection refused: connect. Caused by exception class java.net.ConnectException:
Connection refused: connect
> > FAILURES!!!
> > Tests run: 2,  Failures: 0,  Errors: 1
> When run with jdk131, the test hangs for two hours and then times out, but no error is
reported and hence it appears to "pass".
> When run with ibm142 and jdk142, the test completes without error as expected.

-- 
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