[
https://issues.apache.org/jira/browse/SQOOP-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14236524#comment-14236524
]
Hudson commented on SQOOP-1844:
-------------------------------
UNSTABLE: Integrated in Sqoop2-hadoop200 #641 (See
[https://builds.apache.org/job/Sqoop2-hadoop200/641/])
SQOOP-1844: Sqoop2: Start Derby server in DerbyProvider on random port (abe:
https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=2ce59da58fea98af2c1e236b166fe130676083b4)
* common-test/src/main/java/org/apache/sqoop/common/test/utils/NetworkUtils.java
* common-test/src/main/java/org/apache/sqoop/common/test/db/DerbyProvider.java
> Sqoop2: Start Derby server in DerbyProvider on random port
> ----------------------------------------------------------
>
> Key: SQOOP-1844
> URL: https://issues.apache.org/jira/browse/SQOOP-1844
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.99.4
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Fix For: 1.99.5
>
> Attachments: SQOOP-1844.patch
>
>
> We're currently starting Derby's server for test purpose on one specific port
> - 1527. I found it particularly troublesome in SQOOP-1840 and SQOOP-1816
> where the given port has been used and Derby had troubles to report startup
> problems. However the issue is more generic - binding to single port means
> that one can't possibly run two tests at the same time as they would be
> stepping over each other. Hence I would like to propose to add a test utility
> that will return a "random" available port on the machine and configure
> {{DerbyProvider}} to use that. I'm assuming that such utility will be handy
> even for future tests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
