Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <473035555.1234537800249.JavaMail.jira@brutus>
Date: Fri, 13 Feb 2009 07:10:00 -0800 (PST)
From: "Steve Loughran (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-5254) Xinclude setup results in a stack
 trace
In-Reply-To: <1579549700.1234537559921.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-5254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673258#action_12673258 ] 

Steve Loughran commented on HADOOP-5254:
----------------------------------------

This is the root cause of another test failure of mine, something that tried to load every class that namenode needed, one by one, and resources, and told me off if they were missing. Class.forName("org.apache.hadoop.hdfs.protocol.FSConstants") was throwing an CNFE, but the .class file was around. 

Looks like an ExceptionInInitializerError gets turned into a ClassNotFoundException in Class.forName(), without any attempt to nest in the underlying exception. Because that woudl be too helpful.

Caused by: java.lang.ClassNotFoundException: forName: loading of org.apache.hadoop.hdfs.protocol.FSConstants failed, but loading it without references succeeded. Check references.
at org.smartfrog.sfcore.security.SFClassLoader.forName(SFClassLoader.java:570)
at org.smartfrog.services.os.java.LoadClassImpl.loadClasses(LoadClassImpl.java:160)
at org.smartfrog.services.os.java.LoadClassImpl.loadResourcesAndClasses(LoadClassImpl.java:118)
at org.smartfrog.services.os.java.LoadClassImpl.sfStart(LoadClassImpl.java:104)
at org.smartfrog.services.assertions.TestCompoundImpl.sfStart(TestCompoundImpl.java:248)
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:305)
at sun.rmi.transport.Transport$1.run(Transport.java:159)

> Xinclude setup results in a stack trace
> ---------------------------------------
>
>                 Key: HADOOP-5254
>                 URL: https://issues.apache.org/jira/browse/HADOOP-5254
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: conf
>    Affects Versions: 0.21.0
>            Reporter: Steve Loughran
>
> seen this in SVN_HEAD, and it was mentioned on the user list in the week. It explains why my health tests are failing on class.ForName(FSConstants)
> gistration(127.0.0.1:8024, storageID=DS-1466307248-127.0.1.1-8024-1234537374021, infoPort=8022, ipcPort=50020):DataXceiver
> [sf-startdaemon-debug] java.lang.ExceptionInInitializerError
> [sf-startdaemon-debug] 	at org.apache.hadoop.hdfs.server.datanode.DataXceiver.run(DataXceiver.java:76)
> [sf-startdaemon-debug] 	at java.lang.Thread.run(Thread.java:619)
> [sf-startdaemon-debug] Caused by: java.lang.UnsupportedOperationException: This parser does not support specification "null" version "null"
> [sf-startdaemon-debug] 	at javax.xml.parsers.DocumentBuilderFactory.setXIncludeAware(DocumentBuilderFactory.java:590)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.