[
https://issues.apache.org/jira/browse/SQOOP-1844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14236262#comment-14236262
]
Jarek Jarcec Cecho commented on SQOOP-1844:
-------------------------------------------
You're correct then if there is a zombie process, we should clean it up
[~stanleyxu2005]. In my case, the problem is that there is something funky
going on on my machine, which I feel is outside of the test infrastructure. I
believe that running Derby on randomized port is generally useful as it will
enable us to eventually run the tests in the parallel. You're right that it's
not currently entirely feasible though, but we are slowly getting there - for
example recent SQOOP-1832 is also step in this direction :)
> 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)
