You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kristian Waagan (JIRA)" <ji...@apache.org> on 2007/04/20 10:46:15 UTC
[jira] Commented: (DERBY-2568) 'Connection refused' in
jdbcapi/LobStreamsTest.junit
[ https://issues.apache.org/jira/browse/DERBY-2568?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12490271 ]
Kristian Waagan commented on DERBY-2568:
----------------------------------------
This is my earlier announced test failure due to the DERBY-2346 commit.
The reason is that LobStreamsTest.suite was changed from running embedded only to both embedded and client/server.
Since the test is run both through the old harness and as a pure JUnit test, the two harnesses get in each others way. I guess both the old harness and the JUnit harness is trying to start/stop the network server when run in the old harness.
Note that the test runs fine as part of jdbcapi/_Suite (for "all" JVMs I think).
I would like some input on what to do with this. My take currently is to remove the test from encodingTests in the old harness, as that suite/test has been reported to be invalid (setting a read-only property to change the encoding).
> 'Connection refused' in jdbcapi/LobStreamsTest.junit
> ----------------------------------------------------
>
> Key: DERBY-2568
> URL: https://issues.apache.org/jira/browse/DERBY-2568
> Project: Derby
> Issue Type: Bug
> Components: Regression Test Failure
> Affects Versions: 10.3.0.0
> Environment: OS: ALL
> JVM: Sun Microsystems Inc. 1.5.0_07-b03
> Reporter: Ole Solberg
>
> See http://dbtg.thresher.com/derby/test/Daily/jvm1.5/testing/Limited/testSummary-530466.html, http://dbtg.thresher.com/derby/test/trunk15/jvm1.5/testing/Limited/testSummary-530497.html .
> Ok on JVM: Sun Microsystems Inc. 1.6.0_01-b06, Sun Microsystems Inc. 1.4.2_02-b03.
> <method>
> jdbcapi/LobStreamsTest.junit
> </method>
> <signature>
> > % LobStreamsTest:clientjava.sql.SQLException: java.net.ConnectException : Error connecting to server xxxFILTERED_HOSTNAMExxx on port 1527 with message Connection refused.
> > Caused by: org.apache.derby.client.am.DisconnectException: java.net.ConnectException : Error connecting to server xxxFILTERED_HOSTNAMExxx on port 1527 with message Connection refused.
> > %
> > Caused by: java.net.ConnectException: Connection refused
> > %
> </signature>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.