[
https://issues.apache.org/jira/browse/DERBY-5144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009638#comment-13009638
]
Knut Anders Hatlen commented on DERBY-5144:
-------------------------------------------
I've disabled the testing against JCC in the nightly tests for now, so that we
can eliminate that it's causing the problems. Unfortunately, one cannot disable
JCC testing without also disabling testing of the 10.0 version of the network
server.
> Intermittent "connection refused" errors in the compatibility tests
> -------------------------------------------------------------------
>
> Key: DERBY-5144
> URL: https://issues.apache.org/jira/browse/DERBY-5144
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.8.0.0
> Environment: Compatibility tests on Linux.
> Sun Java 1.5.0, 1.6.0.
> Reporter: Knut Anders Hatlen
>
> The compatibility tests fail intermittently with connection refused errors.
> I've only seen it happening on Linux so far.
> Example failures:
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/testlog/lin/902174-compatibility_diff.txt
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/testlog/sles/1079439-compatibility_diff.txt
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/testlog/sles/1080669-compatibility_diff.txt
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/testlog/sles/1081468-compatibility_diff.txt
> http://dbtg.foundry.sun.com/derby/test/Daily/jvm1.6/testing/testlog/lin/1083233-compatibility_diff.txt
> The stack trace always looks like this:
> Exception in thread "main" com.ibm.db2.jcc.c.SqlException:
> java.net.ConnectException : Error opening socket to server localhost on port
> 1527 with message : Connection refused
> at com.ibm.db2.jcc.a.a.<init>(a.java:135)
> at com.ibm.db2.jcc.a.b.a(b.java:1542)
> at com.ibm.db2.jcc.c.o.<init>(o.java:795)
> at com.ibm.db2.jcc.a.b.<init>(b.java:298)
> at com.ibm.db2.jcc.DB2Driver.connect(DB2Driver.java:162)
> at java.sql.DriverManager.getConnection(DriverManager.java:582)
> at java.sql.DriverManager.getConnection(DriverManager.java:154)
> at
> org.apache.derbyTesting.functionTests.util.DerbyJUnitTest.createDB(DerbyJUnitTest.java:416)
> at
> org.apache.derbyTesting.functionTests.tests.junitTests.compatibility.CompatibilitySuite.access$000(CompatibilitySuite.java:41)
> at
> org.apache.derbyTesting.functionTests.tests.junitTests.compatibility.CompatibilitySuite$Creator.main(CompatibilitySuite.java:448)
> The actual combination in which it fails varies. The reports mentioned above
> show failures in these combinations:
> jdk1.5 + server 10.1.3.1
> jdk1.6 + server 10.1.3.1
> jdk1.6 + server 10.5.1.1
> jdk1.5 + server 10.0.2.1
> jdk1.5 + server 10.7.1.1
> The client that fails is always JCC, but that's because it's always the first
> client to be tested on each server version.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
