[
https://issues.apache.org/jira/browse/HADOOP-5254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12681689#action_12681689
]
Steve Loughran commented on HADOOP-5254:
----------------------------------------
The extra diagnostics flag up that some XML parsers (xerces 2.6.2?) can wait
until a document is created before bailing out; this could be a sign of factory
problems rather than just XML parser support issues; looking at the CP there
are two Xerces versions there (2.6.2. and 2.9.1); clearly the wrong one is
being used.
{code}
09/03/13 12:01:04 [JobTracker] FATAL conf.Configuration : Error parsing
configuration resource core-default.xml :
javax.xml.parsers.ParserConfigurationException: Feature
'http://apache.org/xml/features/xinclude' is not recognized.
javax.xml.parsers.ParserConfigurationException: Feature
'http://apache.org/xml/features/xinclude' is not recognized.
at
org.apache.xerces.jaxp.DocumentBuilderFactoryImpl.newDocumentBuilder(Unknown
Source)
at
org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:1063)
at
org.apache.hadoop.conf.Configuration.loadResources(Configuration.java:1032)
at org.apache.hadoop.conf.Configuration.getProps(Configuration.java:982)
at org.apache.hadoop.conf.Configuration.get(Configuration.java:384)
at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:805)
at org.apache.hadoop.conf.Configuration.getClass(Configuration.java:835)
at
org.apache.hadoop.mapred.JobTracker.getInstrumentationClass(JobTracker.java:1633)
at org.apache.hadoop.mapred.JobTracker.innerStart(JobTracker.java:1472)
at org.apache.hadoop.util.Service.start(Service.java:186)
{code}
# We could check in the extra diagnostics here -stack trace and file at fault;
this will help others
# We could have a catch for a ParserConfigurationException and include an error
message that points the viewer at a wiki page where we point to this bugrep and
anything else relevant
> 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
> Assignee: 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.
