sqoop-dev mailing list archives

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

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

ASF subversion and git services commented on SQOOP-1850:
--------------------------------------------------------

Commit 5f58a1d462caeeb5fd53449682115aacb1b063ff in sqoop's branch refs/heads/sqoop2 from [~jarcec]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=5f58a1d ]

SQOOP-1850: Sqoop2: DerbyProvider retry ping

(Abraham Elmahrek via Jarek Jarcec Cecho)


> 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