You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Veena Basavaraj (JIRA)" <ji...@apache.org> on 2014/12/08 18:09:13 UTC

[jira] [Resolved] (SQOOP-1838) Sqoop2: While running Integration tests in IDE ( we get Derby Start Error)

     [ https://issues.apache.org/jira/browse/SQOOP-1838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Veena Basavaraj resolved SQOOP-1838.
------------------------------------
    Resolution: Fixed

> Sqoop2: While running Integration tests in IDE ( we get Derby Start Error)
> --------------------------------------------------------------------------
>
>                 Key: SQOOP-1838
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1838
>             Project: Sqoop
>          Issue Type: Bug
>    Affects Versions: 1.99.4
>            Reporter: Veena Basavaraj
>            Assignee: Veena Basavaraj
>             Fix For: 1.99.5
>
>
> [~richard_zhou] and I run integration tests in IDE and find that intermittently we ger derby start error
> {code}
>   @Override
>   public void start() {
>     // Start embedded server
>     try {
>       server = new NetworkServerControl(InetAddress.getByName("localhost"), 1527);
>       server.start(new LoggerWriter(LOG, Level.INFO));
>       // Start won't thrown an exception in case that it fails to start, one
>       // have to explicitly call ping() in order to verify if the server is
>       // up. Check DERBY-1465 for more details.
>       server.ping();
>     } catch (Exception e) {
>       LOG.error("Can't start Derby network server", e);
>       throw new RuntimeException("Can't derby server", e);
>     }
> {code}
> The fix is simple to have a thread.sleep until it can start



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