[jira] [Commented] (SQOOP-1844) Sqoop2: Start Derby server in DerbyProvider on random port

["Qian Xu (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SQOOP-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14235064#comment-14235064 ] 

Qian Xu commented on SQOOP-1844:
--------------------------------

Using a random port does help to solve the problem. But we still have zombie test process there, right? Just a thought: If tests can fail fast, when finding specified port is occupied or timeout to start test process, I think we know how to kill zombie test process.

> 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)