[
https://issues.apache.org/jira/browse/SQOOP-1840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14236502#comment-14236502
]
Sqoop QA bot commented on SQOOP-1840:
-------------------------------------
Testing file
[SQOOP-1840.patch|https://issues.apache.org/jira/secure/attachment/12684975/SQOOP-1840.patch]
against branch sqoop2 took 0:00:24.242788.
{color:red}Overall:{color} -1 due to an error
{color:red}ERROR:{color} failed to apply patch (exit code 1):
{code}error: patch failed:
common-test/src/main/java/org/apache/sqoop/common/test/db/DerbyProvider.java:23
error:
common-test/src/main/java/org/apache/sqoop/common/test/db/DerbyProvider.java:
patch does not apply
{code}
{color:green}SUCCESS:{color} Clean was successful
Console output is available
[here|https://builds.apache.org/job/PreCommit-SQOOP-Build/707/console].
This message is automatically generated.
> Sqoop2: Guard test DerbyProvider from infinite waits in Derby implementation
> ----------------------------------------------------------------------------
>
> Key: SQOOP-1840
> URL: https://issues.apache.org/jira/browse/SQOOP-1840
> 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-1840.patch, SQOOP-1840.patch
>
>
> This is pretty much follow up on SQOOP-1816 where I was facing situation that
> calling {{DriverManager.getConnection()}} for {{DerbyProvider}} would wait
> forever in case that Derby server failed to start. I've solved that in
> SQOOP-1816 by adding explicit call to {{ping()}} method that is suppose to
> throw an exception in case that the server is not available. At that time it
> solved my issue, but now the problem is back and I'm observing similar
> infinite wait inside the {{ping()}} call itself.
> I'm not sure what exactly is going wrong with on machine, but it's making the
> tests very unreliable. I've tried to google about the problem, but without
> much luck and hence I would like to propose to make the {{DerbyProvider}}
> smarter and prevent the infinite wait by calling certain "dangerous" methods
> with explicit timeout.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
