Thanks Ram, Setting that system property solved the issue. Thanks, Murali Krishna
________________________________ From: Ram Kulbak <ram.kul...@gmail.com> To: core-user@hadoop.apache.org Sent: Wednesday, 24 June, 2009 7:29:37 PM Subject: Re: Hadoop 0.20.0, xml parsing related error Hi, The exception is a result of having xerces in the classpath. To resolve, make sure you are using Java 6 and set the following system property: -Djavax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl This can also be resolved by the Configuration class(line 1045) making sure it loads the DocumentBuilderFactory bundled with the JVM and not a 'random' classpath-dependent factory.. Hope this helps, Ram On Wed, Jun 24, 2009 at 6:42 PM, murali krishna <muralikpb...@yahoo.com>wrote: > Hi, > > Recently migrated to hadoop-0.20.0 and I am facing > https://issues.apache.org/jira/browse/HADOOP-5254 > > Failed to set setXIncludeAware(true) for parser > org.apache.xerces.jaxp.documentbuilderfactoryi...@1e9e5c73:java.lang.UnsupportedOperationException: > This parser does not support specification "null" version "null" > java.lang.UnsupportedOperationException: This parser does not support > specification "null" version "null" > at > javax..xml.parsers.DocumentBuilderFactory.setXIncludeAware(DocumentBuilderFactory..java:590) > at > org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:1053) > > > So I tried including xml-apis-1.3.04.jar:xerces-2_9_1/xercesImpl.jar in > hadoop classpath. But it started throwing another exception > > 09/06/23 05:53:02 FATAL conf.Configuration: error parsing conf file: > javax.xml.parsers.ParserConfigurationException: Feature ' > http://apache.org/xml/features/xinclude' is not recognized. > Exception in thread "main" java..lang.RuntimeException: > javax.xml.parsers.ParserConfigurationException: Feature ' > http://apache.org/xml/features/xinclude' is not recognized. > at > org.apache.hadoop.conf.Configuration.loadResource(Configuration.java:1170) > > The former one was caught and WARN msg was logged by Configuration.java but > later is uncaught and fails. > > What is the correct jar files / versions that should be included to avoid > this? > > Thanks, > Murali >