You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@sqoop.apache.org by "Vinoth Chandar (JIRA)" <ji...@apache.org> on 2014/11/13 22:25:33 UTC

[jira] [Updated] (SQOOP-1727) Log server initialization errors to log4j

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

Vinoth Chandar updated SQOOP-1727:
----------------------------------
    Attachment: SQOOP-1727.patch

> Log server initialization errors to log4j
> -----------------------------------------
>
>                 Key: SQOOP-1727
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1727
>             Project: Sqoop
>          Issue Type: Improvement
>          Components: sqoop2-server
>            Reporter: Vinoth Chandar
>            Priority: Trivial
>         Attachments: SQOOP-1727.patch
>
>
> Had to drill down to code to see what was causing the server crash without the sqoop.log having any exceptions dumped out. Having these also logged to log4j might be good for debugging. 
> My case turned out to be NoClassDefFound for my connector



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