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

Posted to dev@sqoop.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2014/11/13 23:30:34 UTC

[jira] [Commented] (SQOOP-1727) Sqoop2: Log server initialization errors to log4j

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

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

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

SQOOP-1727: Sqoop2: Log server initialization errors to log4j

(Vinoth Chandar via Abraham Elmahrek)


> Sqoop2: 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
>            Assignee: 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)