tomcat部署,代码指向制定目录报错

在tomcat部署时候,server.xml代码指向制定目录,如下图:

启动不错,如:

2019-02-26 14:32:55.820 ERROR org.springframework.web.context.ContextLoader 331 initWebApplicationContext - Context initialization failed org.springframework.beans.factory.BeanDefinitionStoreException: IOException parsing XML document from ServletContext resource [/<NONE>]; nested exception is java.io.FileNotFoundException: Could not open ServletContext resource [/<NONE>]
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:344) ~[spring-beans.jar:4.1.6.RELEASE]
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304) ~[spring-beans.jar:4.1.6.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181) ~[spring-beans.jar:4.1.6.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:217) ~[spring-beans.jar:4.1.6.RELEASE]
at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:188) ~[spring-beans.jar:4.1.6.RELEASE]
at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:125) ~[spring-web.jar:4.1.6.RELEASE]
at org.springframework.web.context.support.XmlWebApplicationContext.loadBeanDefinitions(XmlWebApplicationContext.java:94) ~[spring-web.jar:4.1.6.RELEASE]
at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:129) ~[spring-context.jar:4.1.6.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:537) ~[spring-context.jar:4.1.6.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:452) ~[spring-context.jar:4.1.6.RELEASE]
at org.springframework.web.context.ContextLoader.configureAndRefreshWebApplicationContext(ContextLoader.java:403) ~[spring-web.jar:4.1.6.RELEASE]
at org.springframework.web.context.ContextLoader.initWebApplicationContext(ContextLoader.java:306) [spring-web.jar:4.1.6.RELEASE]
at org.springframework.web.context.ContextLoaderListener.contextInitialized(ContextLoaderListener.java:106) [spring-web.jar:4.1.6.RELEASE]
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4790) [catalina.jar:8.5.32]
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5256) [catalina.jar:8.5.32]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) [catalina.jar:8.5.32]
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1421) [catalina.jar:8.5.32]
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1411) [catalina.jar:8.5.32]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_91]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_91]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_91]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_91]
Caused by: java.io.FileNotFoundException: Could not open ServletContext resource [/<NONE>]
at org.springframework.web.context.support.ServletContextResource.getInputStream(ServletContextResource.java:141) ~[spring-web.jar:4.1.6.RELEASE]
at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:330) ~[spring-beans.jar:4.1.6.RELEASE]
... 21 more

26-Feb-2019 14:32:55.830 严重 [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file
26-Feb-2019 14:32:55.846 严重 [localhost-startStop-1] org.apache.catalina.core.StandardContext.startInternal Context [/fenlibao] startup failed due to previous errors
2019-02-26 14:32:55.871 INFO org.springframework.context.support.AbstractApplicationContext 862 doClose - Closing Root WebApplicationContext: startup date [Tue Feb 26 14:32:55 CST 2019]; root of context hierarchy
2019-02-26 14:32:55.881 WARN org.springframework.context.support.AbstractApplicationContext 872 doClose - Exception thrown from ApplicationListener handling ContextClosedEvent java.lang.IllegalStateException: ApplicationEventMulticaster not initialized - call ‘refresh‘ before multicasting events via the context: Root WebApplicationContext: startup date [Tue Feb 26 14:32:55 CST 2019]; root of context hierarchy
at org.springframework.context.support.AbstractApplicationContext.getApplicationEventMulticaster(AbstractApplicationContext.java:344) ~[spring-context.jar:4.1.6.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:331) ~[spring-context.jar:4.1.6.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.doClose(AbstractApplicationContext.java:869) [spring-context.jar:4.1.6.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.close(AbstractApplicationContext.java:836) [spring-context.jar:4.1.6.RELEASE]
at org.springframework.web.context.ContextLoader.closeWebApplicationContext(ContextLoader.java:579) [spring-web.jar:4.1.6.RELEASE]
at org.springframework.web.context.ContextLoaderListener.contextDestroyed(ContextLoaderListener.java:115) [spring-web.jar:4.1.6.RELEASE]
at org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:4837) [catalina.jar:8.5.32]
at org.apache.catalina.core.StandardContext.stopInternal(StandardContext.java:5478) [catalina.jar:8.5.32]
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:226) [catalina.jar:8.5.32]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154) [catalina.jar:8.5.32]
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1421) [catalina.jar:8.5.32]
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1411) [catalina.jar:8.5.32]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_91]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_91]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_91]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_91]

2019-02-26 14:32:55.882 WARN org.springframework.context.support.AbstractApplicationContext 880 doClose - Exception thrown from LifecycleProcessor on context close java.lang.IllegalStateException: LifecycleProcessor not initialized - call ‘refresh‘ before invoking lifecycle methods via the context: Root WebApplicationContext: startup date [Tue Feb 26 14:32:55 CST 2019]; root of context hierarchy
at org.springframework.context.support.AbstractApplicationContext.getLifecycleProcessor(AbstractApplicationContext.java:357) ~[spring-context.jar:4.1.6.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.doClose(AbstractApplicationContext.java:877) [spring-context.jar:4.1.6.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.close(AbstractApplicationContext.java:836) [spring-context.jar:4.1.6.RELEASE]
at org.springframework.web.context.ContextLoader.closeWebApplicationContext(ContextLoader.java:579) [spring-web.jar:4.1.6.RELEASE]
at org.springframework.web.context.ContextLoaderListener.contextDestroyed(ContextLoaderListener.java:115) [spring-web.jar:4.1.6.RELEASE]
at org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:4837) [catalina.jar:8.5.32]
at org.apache.catalina.core.StandardContext.stopInternal(StandardContext.java:5478) [catalina.jar:8.5.32]
at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:226) [catalina.jar:8.5.32]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:154) [catalina.jar:8.5.32]
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1421) [catalina.jar:8.5.32]
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1411) [catalina.jar:8.5.32]
at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_91]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [?:1.8.0_91]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [?:1.8.0_91]
at java.lang.Thread.run(Thread.java:745) [?:1.8.0_91]

解决方案:

将代码直接部署在  tomcat8.5/webapps/ROOT

原文地址:https://www.cnblogs.com/chxish/p/10437231.html

时间: 2025-01-07 00:50:25

tomcat部署,代码指向制定目录报错的相关文章

Linux下编译C代码,出现tan函数报错的情况

undefined reference to `tan' 但是已经包含了头文件 <math.h>了,可还是报错,说是找不到tan 这个问题的原因不是很清楚, 但是网上给出的方案,就是编译的时候 加上参数 -lm 有说l表示Lib ,m表示 math.h  , ****************************************************************************************************** 以下是一些说明 使用math.h

使用Entity Framework迁移完数据库后,每次修改代码(非模型代码)后都报错。

问题:使用Entity Framework迁移完数据库后,每次修改代码(非模型代码)后都报错: 支持“XXXDbContext”上下文的模型已在数据库创建后发生更改.请考虑使用 Code First 迁移更新数据库(http://go.microsoft.com/fwlink/?LinkId=238269). 这时如果执行 Add-Migration 生成的迁移代码是空的.于是重新Update-Database,结果却是No pending explicit migrations. 不过这时是不

java_tomcat_the_APR based Apache Tomcat 小喵咪死活启动报错_临时方案

报错信息如下: 信息: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: D:\Program Files\Java\jdk1.6.0_33\bin; 造成结果: IDE中无法加载web项目 ,不方便调试. 解决步奏: 1 百度之,各种tcnative-1.dll

tomcat启动找不到jer报错

今天在启动tomcat时候报错, 找不到jarhome 指定的目录配置. : vim etc/profile 这个未修改的时候配置的环境变量: 我们在配置一个jre_home 如下图所示: export JRE_HOME=$JAVA_HOME/jre $JRE_HOME/bin 如果帮助到您了,欢迎转载~ 大家有什么不明白的地方可以给我发送邮件共同探讨,有不足之处也望您及时指出! email: [email protected]

解决cgal中的surface_mesh_deformation,代码copy到别处报错

我只想说我遇到过多少奇葩的bug啊...这么奇葩的错误我竟然能debug出来真是醉醉的 cgal4.5之后,有实现surface_mesh_deformation的example. 1.如何正常编译example? 最好是在编译cgal的时候,cmake中的entry就有,勾选上with_eigen,然后配置include目录即可. 这样以后省事,所以编译cgal的时候,要好好检查外置的库,会用到的都先加上. 如果不想重新编译cgal,在重新用cmake编译surface_mesh_deform

MDT部署Win10最后一阶段报错!求老师,大神们帮看看是哪里的问题!!小弟感激不尽~~~

如题:MDT部署Win10到最后一阶段会报错,具体原因也未指出,能力有限日志又不太会看,只能求助于各位.之前搭建好后测试部署是没任何问题的,由于需要捕获镜像,就研究捕获去了,期间各种捕获失败报错,自己一直尝试总算搞定能正常捕获了,打算用捕获到的镜像去部署,呵呵了,捕获没问题了,结果部署又问题来了,自己各种尝试已经实在无能为力解决不了了. 现在的状态是:从开始部署就一直看着试验机MDT任务执行的情况看着貌似没什么问题,分区以及从服务器copy驱动,copy镜像都能执行完成,到最后感觉就快完成重启时

docker-compose进行部署容器的时候,报错权限不足

刚刚用docker-compose部署elk的时候,没有起来,查看日志的时候,发现在数据卷挂载的时候,报错权限不足. 由于日志不在了,这里就直接贴出解决办法. 问题原因及解决办法 原因是CentOS7中的安全模块selinux把权限禁掉了,至少有以下三种方式解决挂载的目录没有权限的问题: 1.在运行容器的时候,给容器加特权,及加上 --privileged=true 参数: docker run -i -t -v /soft:/soft --privileged=true 686672a1d0c

解决阿里云部署 office web apps ApplicationFailedException 报错问题

查找这个问题,确实花费了很长时间,所以具体解析一下问题原因吧. 报错如下: 问题详情链接 New-OfficeWebAppsFarm:Office Online服务无法启动.有关详细信息,请参阅Windows应用程序事件日志 + New-OfficeWebAppsFarm -InternalUrl"http://"...... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~ + Cat

微软SSIS部署抽取数据的包报错

错误提示: 说明: 无法解密受保护的 XML 节点“DTS:Password”,错误为 0x8009000B“该项不适于在指定状态下使用.”.可能您无权访问此信息.当发生加密错误时会出现此错误.请确保提供正确的密钥.  错误结束  错误: 2019-08-08 11:28:01.04     代码: 0xC0016016     源:       说明: 无法解密受保护的 XML 节点“DTS:Password”,错误为 0x8009000B“该项不适于在指定状态下使用.”.可能您无权访问此信息