[
https://issues.apache.org/jira/browse/DERBY-6095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamta A. Satoor resolved DERBY-6095.
------------------------------------
Resolution: Not A Problem
This was a machine issue. Following is Rick's comment on the machine
******************************************
Hi Mamta,
This looks like an environmental problem in the Oracle test lab which runs
these tests. A subsequent test run (triggered by a later checkin) appears to
have run cleanly. The instability in the test lab needs to be addressed. I'm
afraid I can't tell you when the lab will stabilize.
Thanks,
-Rick
******************************************
> Failures in org.apache.derbyTesting.functionTests.tests.management with
> java.net.ConnectException: Connection timed out exceptions
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-6095
> URL: https://issues.apache.org/jira/browse/DERBY-6095
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.9.2.2
> Reporter: Mamta A. Satoor
> Assignee: Mamta A. Satoor
>
> I backported DERBY-6053 into 10.9 yesterday with revision 1451023. I ran the
> junit tests on my 10.9 client with IBM 1.7 jdk before the checkin and they
> ran fine. But, the Sun's nightly runs after the checkin shows junit tests
> passed with ia32_jdk5 and ia32_jdk6 but failed with
> amd64_jdk7(http://download.java.net/javadesktop/derby/javadb-5573355-report/).
>
> The failures with amd64_jdk7 can be found at
> http://download.java.net/javadesktop/derby/javadb-5573355-report/javadb-5573355-3601031-details.html
> There are 50 tests that failed and they are all from
> org.apache.derbyTesting.functionTests.tests.management and the exception all
> seem to be with connection timeout issue
> java.rmi.ConnectException: Connection refused to host: 10.163.184.120;
> nested exception is:
> java.net.ConnectException: Connection timed out
> I am wondering if this could be a machine issue. I am planning on doing a
> dummy commit into 10.9 so the tests will fire again on Sun's machine(it looks
> like 10.9 test runs happen only when there is a checkin on that codeline) to
> see how the tests go with amd64_jdk7.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
