hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-5254) Xinclude setup results in a stack trace
Date Fri, 13 Feb 2009 21:41:02 GMT

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

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

I've only done it against trunk; not looked at 0.20. 

It would be nice to have some details on what triggers the problem; which JVMs do/dont exhibit
this problem.

# all the hadoop core tests worked
# my single VM tests worked
# it was the stuff trying to deploy and test onto a VM-ware hosted image that caused problems.

# Once I pushed xerces2.9.1 onto the classpath, things went away

I think the hadoop core tests aren't noticing this because Ant ships with xerces; junit-under-ant
gets tht when you tell junit to inherit Ant's classpath. 
My VM tests may have been working for the same reason. 
It was only the stuff running standalone that was in trouble.

I'll ask around -what we need is a table that shows JDK and Xerces versions with features
in each


> 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.20.0, 0.21.0
>         Environment: java version "1.6.0_02"
> Java(TM) SE Runtime Environment (build 1.6.0_02-b05)
> BEA JRockit(R) (build R27.4.0-90-89592-1.6.0_02-20070928-1715-linux-x86_64, compiled
mode)
>            Reporter: Steve Loughran
>         Attachments: hadoop-5254.patch
>
>
> 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.


Mime
View raw message