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 "Andrew McIntyre (JIRA)" <ji...@apache.org> on 2007/03/24 05:37:32 UTC
[jira] Resolved: (DERBY-2418) TestProto.java used by
testProtocol.java hardcodes port 1527
[ https://issues.apache.org/jira/browse/DERBY-2418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew McIntyre resolved DERBY-2418.
------------------------------------
Resolution: Fixed
Fix Version/s: 10.3.0.0
Derby Info: (was: [Patch Available])
Committed _try2 patch to trunk with revision 521977
> TestProto.java used by testProtocol.java hardcodes port 1527
> ------------------------------------------------------------
>
> Key: DERBY-2418
> URL: https://issues.apache.org/jira/browse/DERBY-2418
> Project: Derby
> Issue Type: Improvement
> Components: Test
> Reporter: Dag H. Wanvik
> Assigned To: Julius Stroffek
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: d2418.diff, d2418.stat, d2418_try2.diff, d2418_try2.stat
>
>
> NetHarnessJavaTest reuses the old framework test 'testProtocol' via
> old framework adapter HarnessJavaTest.
> testProtocol uses the class TestProto which hardcodes use of port 1527.
> It would be nice to pass the port used in the current TestConfiguration
> to testProtocol/TestProto so the JUnit suites can move towards being runnable
> with another port than the default.
> Currently, using another port than 1527 for TestConfiguration.DEFAULT_PORT,
> the test fails and crashes JUnit's TestRunner with the console message:
> Couldn't get I/O for the connection to: localhost
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.