On 10/2/06, A B (JIRA) <[email protected]> wrote:
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
Army, Does this test show the same behavior with 10.2? Reason for asking is that we had said we'd stop support for jdk131 based jvms with 10.3...So, 10.2 would be the last version this would be relevant for. Myrna
