Eclipse Tomcat Project报错：HTTP Status 404错误

想要在eclipse里部署tomcat，结果tomcat单独可以通过连接测试，用eclipse就404了

404肯定都是目录不对，试了半天在eclipse下改了一下配置和文件位置就行了

1.先在菜单栏停止tomcat，之后在屏幕下方选中Servers，删掉正在运行的项目

2.右键点开服务器，应该是下图的状态

Server Locations一定要选第二个

Server Path要对应tomcat的安装目录

Deploy Path改为：webapps

3.eclipse里的文件组织是这样：

时间： 2025-01-10 23:13:46

Eclipse Tomcat Project报错：HTTP Status 404错误的相关文章

TOMCAT报错:HTTP Status 404 -

构建struts2工程师,tomcat报错: HTTP Status 404 - type Status report message description The requested resource is not available. Apache Tomcat/6.0.37

Eclipse Maven项目报错2之A child container failed during start

问题:在同事那里拿了一个Eclipse的maven项目,导入报错,主要显示的是A child container failed during start 具体错误如下六月 02, 2018 12:08:50 下午 org.apache.tomcat.util.digester.SetPropertiesRule begin 警告: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'source'

Tomcat启动报错[org.apache.struts2.dispatcher.Dispatcher]Dispatcher initialization failed

Tomcat启动报错: [org.apache.struts2.dispatcher.Dispatcher]Dispatcher initialization failed Unable to load configuration. - bean - jar:file:/E:/SoftwareDevelopment/Software/Eclipse4.3/eclipse-jee-kepler-SR1-win32-x86_64/Workspace/.metadata/.plugins/org.ec

启动Tomcat服务器报错

启动Tomcat服务器报错: Several ports (8005, 8080, 8009) required by Tomcat v5.5 Server at localhost are already in use. The server may already be running in another process, or a system process may be using the port. To start this server you will need to sto

Android 启动Tomcat服务报错，端口占用解决方案

启动Tomcat服务器报错:Several ports (8005, 8080, 8009) required by Tomcat v5.5 Server at localhost are already in use. The server may already be running in another process, or a system process may be using the port. To start this server you will need to stop

报错：struts 404

错误信息:HTTP Status 404 - There is no Action mapped for namespace [/] and action name [updateUser!getUserByName] associated with context path [/123shop]. 报错:struts 404,布布扣,bubuko.com

tomcat启动报错，找不到相应的 queue，从而引发内存泄漏

tomcat启动报错,无法创建 bean listenerStatusChangeDealHandler, no queue 'STOCK.NOTIFY_CHANGE.INTER.CACHE.QUEUE' in vhost 从启动日志来看,有时候仅会看到内存泄漏,而没有与queue相关的日志,非常easy走错方向. 依照 http://blog.csdn.net/wangjunjun2008/article/details/23375501 的方法能够看到具体日志,从而确定报错原因 tomcat

tomcat启动报错，找不到对应的 queue，从而引发内存泄漏

tomcat启动报错,无法创建 bean listenerStatusChangeDealHandler, no queue 'STOCK.NOTIFY_CHANGE.INTER.CACHE.QUEUE' in vhost 从启动日志来看,有时候仅会看到内存泄漏,而没有与queue相关的日志,很容易走错方向. 按照 http://blog.csdn.net/wangjunjun2008/article/details/23375501 的方法可以看到详细日志,从而确定报错原因 tomcat启动报

log4j的1.2.15版本，在pom.xml中的顶层project报错错误： Failure to transfer javax.jms:jms:jar:1.1 from https://maven-repository.dev.java.net/nonav/repository......

在动态网站工程中,添加了Pom依赖,当添加log4j的1.2.15版本依赖时,在pom.xml中的顶层project报错错误: Failure to transfer javax.jms:jms:jar:1.1 from https://maven-repository.dev.java.net/nonav/repository......,如下图这是因为 https://maven-repository.dev.java.net/nonav/repository 这个域名已经无法解析了. 而