简体   繁体   English

雄猫。 此解析器不支持规范 null 版本 null

[英]Tomcat. This parser does not support specification null version null

I try to run a web application on oracle linux, tomcat 7 and jdk1.7 and I get an exception on first page load after tomcat restart.我尝试在 oracle linux、tomcat 7 和 jdk1.7 上运行一个 Web 应用程序,在 tomcat 重启后我在第一页加载时遇到异常。 The exception occurs only at first application pageload.该异常仅在首次应用程序页面加载时发生。 Application is developed on jdk1.6 and on a server is installed jdk1.4-compact and jdk1.7 but I entered jdk1.7 path to JAVA_HOME and JRE_HOME in tomcat/bin/setclasspath.sh file.应用程序是在 jdk1.6 上开发的,在服务器上安装了 jdk1.4-compact 和 jdk1.7,但我在tomcat/bin/setclasspath.sh文件中输入了 jdk1.7 到 JAVA_HOME 和 JRE_HOME 的路径。 Any ideas why I am getting this exception?任何想法为什么我会收到此异常?

Jan 03, 2012 5:11:28 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 10261 ms
Jan 03, 2012 5:15:49 PM org.apache.commons.digester.Digester getParser
SEVERE: Digester.getParser: 
java.lang.UnsupportedOperationException: This parser does not support specification "null" version "null"
    at javax.xml.parsers.SAXParserFactory.setSchema(SAXParserFactory.java:419)
    at org.apache.commons.digester.Digester.getFactory(Digester.java:541)
    at org.apache.commons.digester.Digester.getParser(Digester.java:791)
    at org.apache.commons.digester.Digester.getXMLReader(Digester.java:1068)
    at org.apache.commons.digester.Digester.parse(Digester.java:1916)
    at org.apache.tiles.definition.digester.DigesterDefinitionsReader.read(DigesterDefinitionsReader.java:329)
    at org.apache.tiles.definition.dao.BaseLocaleUrlDefinitionDAO.loadDefinitionsFromURL(BaseLocaleUrlDefinitionDAO.java:276)
    at org.apache.tiles.definition.dao.CachingLocaleUrlDefinitionDAO.loadDefinitionsFromURLs(CachingLocaleUrlDefinitionDAO.java:251)
    at org.apache.tiles.definition.dao.ResolvingLocaleUrlDefinitionDAO.loadDefinitionsFromURLs(ResolvingLocaleUrlDefinitionDAO.java:65)
    at org.apache.tiles.definition.dao.ResolvingLocaleUrlDefinitionDAO.loadParentDefinitions(ResolvingLocaleUrlDefinitionDAO.java:58)
    at org.apache.tiles.definition.dao.CachingLocaleUrlDefinitionDAO.loadDefinitionsFromURLs(CachingLocaleUrlDefinitionDAO.java:239)
    at org.apache.tiles.definition.dao.ResolvingLocaleUrlDefinitionDAO.loadDefinitionsFromURLs(ResolvingLocaleUrlDefinitionDAO.java:65)
    at org.apache.tiles.definition.dao.ResolvingLocaleUrlDefinitionDAO.loadParentDefinitions(ResolvingLocaleUrlDefinitionDAO.java:58)
    at org.apache.tiles.definition.dao.CachingLocaleUrlDefinitionDAO.loadDefinitionsFromURLs(CachingLocaleUrlDefinitionDAO.java:239)
    at org.apache.tiles.definition.dao.ResolvingLocaleUrlDefinitionDAO.loadDefinitionsFromURLs(ResolvingLocaleUrlDefinitionDAO.java:65)
    at org.apache.tiles.definition.dao.CachingLocaleUrlDefinitionDAO.loadDefinitions(CachingLocaleUrlDefinitionDAO.java:222)
    at org.apache.tiles.definition.dao.CachingLocaleUrlDefinitionDAO.checkAndloadDefinitions(CachingLocaleUrlDefinitionDAO.java:204)
    at org.apache.tiles.definition.dao.CachingLocaleUrlDefinitionDAO.getDefinitions(CachingLocaleUrlDefinitionDAO.java:154)
    at org.apache.tiles.definition.dao.CachingLocaleUrlDefinitionDAO.getDefinition(CachingLocaleUrlDefinitionDAO.java:123)
    at org.apache.tiles.definition.dao.CachingLocaleUrlDefinitionDAO.getDefinition(CachingLocaleUrlDefinitionDAO.java:54)
    at org.apache.tiles.definition.UnresolvingLocaleDefinitionsFactory.getDefinition(UnresolvingLocaleDefinitionsFactory.java:105)
    at org.apache.tiles.impl.BasicTilesContainer.getDefinition(BasicTilesContainer.java:364)
    at org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:618)
    at org.apache.tiles.impl.BasicTilesContainer.render(BasicTilesContainer.java:321)
    at org.apache.struts2.views.tiles.TilesResult.doExecute(TilesResult.java:105)
    at org.apache.struts2.dispatcher.StrutsResultSupport.execute(StrutsResultSupport.java:186)
    at com.opensymphony.xwork2.DefaultActionInvocation.executeResult(DefaultActionInvocation.java:373)
    at com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:277)
    at org.apache.struts2.impl.StrutsActionProxy.execute(StrutsActionProxy.java:52)
    at org.apache.struts2.dispatcher.Dispatcher.serviceAction(Dispatcher.java:485)
    at org.apache.struts2.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:395)
    at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243)
    at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210)
    at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:224)
    at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:169)
    at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472)
    at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:168)
    at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:100)
    at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:929)
    at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118)
    at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:405)
    at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:200)
    at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:515)
    at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:302)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
    at java.lang.Thread.run(Thread.java:722)

Do you have two xml digester on classpath?你在类路径上有两个 xml 摘要器吗? Try removing one.尝试删除一个。

There are some significant library change (I don't know in details)from jdk1.6 to jdk1.7.从 jdk1.6 到 jdk1.7 有一些重要的库变化(我不知道细节)。 I faced the similar types of problem in my system also.我的系统中也遇到了类似的问题。 For temporary work around you can just point jdk1.6 in JAVA_HOME and JRE_HOME instead of jdk 1.7对于临时工作,您可以将 jdk1.6 指向 JAVA_HOME 和 JRE_HOME 而不是 jdk 1.7

This issue comes due to javasist version conflict.这个问题是由于 javasist 版本冲突造成的。 Add exclusion in your theamleasf artifact, It will solve your issue.在您的 theamleasf 工件中添加排除项,它将解决您的问题。

I was getting the same issue while deploying one war from Tomcat(8.5.60) and the one thing which worked for me was that I added below properties in %APACHE_HOME%\\conf\\catalina.properties file and restarted tomcat -我在从 Tomcat(8.5.60)部署一场战争时遇到了同样的问题,对我有用的一件事是我在 %APACHE_HOME%\\conf\\catalina.properties 文件中添加了以下属性并重新启动了 tomcat -

javax.xml.parsers.DocumentBuilderFactory=com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl
javax.xml.transform.TransformerFactory=com.sun.org.apache.xalan.internal.xsltc.trax.TransformerFactoryImpl
javax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
javax.xml.datatype.DatatypeFactory=com.sun.org.apache.xerces.internal.jaxp.datatype.DatatypeFactoryImpl

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 XSD验证:此解析器不支持规范“null”版本“null” - XSD Validation: This parser does not support specification “null” version “null” 在tomcat中部署的问题。 在本地tomcat中工作正常。 在生产tomcat中抛出空指针异常 - issue with deployment in tomcat. Works fine in local tomcat. throws null pointer exception in Production tomcat 雄猫 在Eclipse中工作,但在部署时不工作 - Tomcat. Works in Eclipse, but does not work when deployed 雄猫。 Java运行时编译 - Tomcat. Java runtime compile Tomcat。 导入 class 时出现 ClassNotFoundException - Tomcat. ClassNotFoundException on importing class XML解析器为空 - XML parser getting null JsonNode Null JsonArray 解析器 - JsonNode Null JsonArray Parser Wildfly 10.0.0最终版本是否支持Tomcat等OCSP? - Does Wildfly 10.0.0 final Version support OCSP like Tomcat? 如何修复 NullPointerException “org.apache.commons.lang3.SystemUtils.JAVA_SPECIFICATION_VERSION_AS_ENUM”是 null? - How to fix NullPointerException “org.apache.commons.lang3.SystemUtils.JAVA_SPECIFICATION_VERSION_AS_ENUM” is null? 该服务器在Eclipse上不支持J2EE Web模块规范的版本3.1。 - The server does not support version 3.1 of the J2EE Web module specification on Eclipse
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM