sqoop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SQOOP-1850) Sqoop2: DerbyProvider retry ping
Date Mon, 08 Dec 2014 17:47:13 GMT

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

Hudson commented on SQOOP-1850:
-------------------------------

UNSTABLE: Integrated in Sqoop2-hadoop200 #643 (See [https://builds.apache.org/job/Sqoop2-hadoop200/643/])
SQOOP-1850: Sqoop2: DerbyProvider retry ping (jarcec: https://git-wip-us.apache.org/repos/asf?p=sqoop.git&a=commit&h=5f58a1d462caeeb5fd53449682115aacb1b063ff)
* common-test/src/main/java/org/apache/sqoop/common/test/db/DerbyProvider.java


> Sqoop2: DerbyProvider retry ping
> --------------------------------
>
>                 Key: SQOOP-1850
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1850
>             Project: Sqoop
>          Issue Type: Bug
>          Components: sqoop2-test
>    Affects Versions: 1.99.5
>            Reporter: Abraham Elmahrek
>            Assignee: Abraham Elmahrek
>             Fix For: 1.99.5
>
>         Attachments: SQOOP-1850.0.patch
>
>
> Sometimes if the server doesn't immediately bind to its port, then "ping" command will
throw an exception and the provider will not start. The "ping" method should be caught and
retried.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message