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/11/13 22:31:33 UTC

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

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

Veena Basavaraj edited comment on SQOOP-1727 at 11/13/14 9:30 PM:
------------------------------------------------------------------

+ 1, this totally makes sense. 


was (Author: vybs):
+ 1

> 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
>    Affects Versions: 1.99.3
>            Reporter: Vinoth Chandar
>            Priority: Trivial
>             Fix For: 1.99.5
>
>         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)