eclipse崩溃后重启访问项目报错This application has no explicit mapping for /error

本文介绍了一次SpringBoot项目启动失败的经历,由于端口被占用导致Tomcat启动失败。文章提供了详细的错误日志,并给出了在Windows环境下如何查找并释放被占用端口的方法。

 

环境:springboot  jdk1.8

重现条件:eclipse卡死崩溃,重启之后,浏览器访问项目

异常现象:

页面报错:

Whitelabel Error Page

This application has no explicit mapping for /error, so you are seeing this as a fallback.

Fri Jul 27 15:45:01 CST 2018

There was an unexpected error (type=Internal Server Error, status=500).

Error creating bean with name 'dorado.htmlViewResolver' defined in class path resource [com/bstek/dorado/view/servlet-context.xml]: Cannot resolve reference to bean 'dorado.velocityHelper' while setting bean property 'velocityHelper'; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dorado.velocityHelper': FactoryBean threw exception on object creation; nested exception is java.lang.IllegalStateException: Illegal access: this web application instance has been stopped already. Could not load [VM_global_library.vm]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.

控制台报错:

2018-07-27 15:58:34.099  INFO 14812 --- [  restartedMain] c.b.dorado.spring.RemovableBeanUtils     : 200 Bean(s) unregisted in 55ms.
2018-07-27 15:58:34.101  INFO 14812 --- [  restartedMain] o.apache.catalina.core.StandardService   : Stopping service [Tomcat]
2018-07-27 15:58:34.109  INFO 14812 --- [ost-startStop-2] o.a.c.c.C.[.[localhost].[/web]     : Destroying Spring FrameworkServlet 'doradoServlet'
2018-07-27 15:58:34.110  INFO 14812 --- [ost-startStop-2] o.s.w.c.s.XmlWebApplicationContext       : Closing WebApplicationContext for namespace 'doradoServlet-servlet': startup date [Fri Jul 27 15:58:31 CST 2018]; parent: org.springframework.boot.web.servlet.context.AnnotationConfigServletWebServerApplicationContext@1ad1464b
2018-07-27 15:58:34.132  WARN 14812 --- [ost-startStop-2] o.a.c.loader.WebappClassLoaderBase       : The web application [web] appears to have started a thread named [Version info send timer] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 java.lang.Object.wait(Native Method)
 java.util.TimerThread.mainLoop(Timer.java:552)
 java.util.TimerThread.run(Timer.java:505)
2018-07-27 15:58:34.132  WARN 14812 --- [ost-startStop-2] o.a.c.loader.WebappClassLoaderBase       : The web application [web] appears to have started a thread named [ZkClient-EventThread-25-10.37.168.136:2181] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
 java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
 com.suning.framework.zookeeper.ZkEventThread.run(ZkEventThread.java:64)
2018-07-27 15:58:34.133  WARN 14812 --- [ost-startStop-2] o.a.c.loader.WebappClassLoaderBase       : The web application [web] appears to have started a thread named [localhost-startStop-1-SendThread(10.37.168.136:2181)] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.nio.ch.WindowsSelectorImpl$SubSelector.poll0(Native Method)
 sun.nio.ch.WindowsSelectorImpl$SubSelector.poll(WindowsSelectorImpl.java:296)
 sun.nio.ch.WindowsSelectorImpl$SubSelector.access$400(WindowsSelectorImpl.java:278)
 sun.nio.ch.WindowsSelectorImpl.doSelect(WindowsSelectorImpl.java:159)
 sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:86)
 sun.nio.ch.SelectorImpl.select(SelectorImpl.java:97)
 org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:349)
 org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1141)
2018-07-27 15:58:34.134  WARN 14812 --- [ost-startStop-2] o.a.c.loader.WebappClassLoaderBase       : The web application [web] appears to have started a thread named [localhost-startStop-1-EventThread] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 sun.misc.Unsafe.park(Native Method)
 java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
 java.util.concurrent.LinkedBlockingQueue.take(LinkedBlockingQueue.java:442)
 org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:501)
2018-07-27 15:58:34.134  WARN 14812 --- [ost-startStop-2] o.a.c.loader.WebappClassLoaderBase       : The web application [web] appears to have started a thread named [Timer-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
 java.lang.Object.wait(Native Method)
 java.util.TimerThread.mainLoop(Timer.java:552)
 java.util.TimerThread.run(Timer.java:505)

2018-07-27 15:58:34.162  INFO 14812 --- [  restartedMain] ConditionEvaluationReportLoggingListener :

Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
2018-07-27 15:58:34.166 ERROR 14812 --- [  restartedMain] o.s.b.d.LoggingFailureAnalysisReporter   :

***************************
APPLICATION FAILED TO START
***************************

Description:

The Tomcat connector configured to listen on port 80 failed to start. The port may already be in use or the connector may be misconfigured.

Action:

Verify the connector's configuration, identify and stop any process that's listening on port 80, or configure this application to listen on another port.

2018-07-27 15:58:34.168  INFO 14812 --- [  restartedMain] ConfigServletWebServerApplicationContext : Closing org.springframework.boot.web.servlet.context.AnnotationConfigServletWebServerApplicationContext@1ad1464b: startup date [Fri Jul 27 15:57:45 CST 2018]; root of context hierarchy
2018-07-27 15:58:34.175  INFO 14812 --- [  restartedMain] o.s.j.e.a.AnnotationMBeanExporter        : Unregistering JMX-exposed beans on shutdown
2018-07-27 15:58:34.176  INFO 14812 --- [  restartedMain] o.s.j.e.a.AnnotationMBeanExporter        : Unregistering JMX-exposed beans
2018-07-27 15:58:34.197  INFO 14812 --- [  restartedMain] j.LocalContainerEntityManagerFactoryBean : Closing JPA EntityManagerFactory for persistence unit 'default'
2018-07-27 15:58:34.199  INFO 14812 --- [  restartedMain] com.zaxxer.hikari.HikariDataSource       : dataSource - Shutdown initiated...
2018-07-27 15:58:34.215  INFO 14812 --- [  restartedMain] com.zaxxer.hikari.HikariDataSource       : dataSource - Shutdown completed.

分析原因:

端口占用。springboot项目,不直接运行tomcat,造成不易发现是端口占用的情况。

解决办法:

windows环境下,使用电脑管家之类的工具,查看网络连接情况,关闭占用端口的进程。

 

 

C:\Users\admin\.jdks\corretto-18.0.2\bin\java.exe -XX:TieredStopAtLevel=1 -Dspring.output.ansi.enabled=always -Dcom.sun.management.jmxremote -Dspring.jmx.enabled=true -Dspring.liveBeansView.mbeanDomain -Dspring.application.admin.enabled=true -javaagent:D:\soft\IntelliJIDEA2022.2.5\lib\idea_rt.jar=51628:D:\soft\IntelliJIDEA2022.2.5\bin -Dfile.encoding=UTF-8 -Dsun.stdout.encoding=UTF-8 -Dsun.stderr.encoding=UTF-8 -classpath D:\javacode\user\target\classes;D:\soft\apache-maven-3.8.8\mvn_resp\org\springframework\boot\spring-boot-starter\3.5.3\spring-boot-starter-3.5.3.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\springframework\boot\spring-boot\3.5.3\spring-boot-3.5.3.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\springframework\spring-context\6.2.8\spring-context-6.2.8.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\springframework\boot\spring-boot-autoconfigure\3.5.3\spring-boot-autoconfigure-3.5.3.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\springframework\boot\spring-boot-starter-logging\3.5.3\spring-boot-starter-logging-3.5.3.jar;D:\soft\apache-maven-3.8.8\mvn_resp\ch\qos\logback\logback-classic\1.5.18\logback-classic-1.5.18.jar;D:\soft\apache-maven-3.8.8\mvn_resp\ch\qos\logback\logback-core\1.5.18\logback-core-1.5.18.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\apache\logging\log4j\log4j-to-slf4j\2.24.3\log4j-to-slf4j-2.24.3.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\apache\logging\log4j\log4j-api\2.24.3\log4j-api-2.24.3.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\slf4j\jul-to-slf4j\2.0.17\jul-to-slf4j-2.0.17.jar;D:\soft\apache-maven-3.8.8\mvn_resp\jakarta\annotation\jakarta.annotation-api\2.1.1\jakarta.annotation-api-2.1.1.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\springframework\spring-core\6.2.8\spring-core-6.2.8.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\springframework\spring-jcl\6.2.8\spring-jcl-6.2.8.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\yaml\snakeyaml\2.4\snakeyaml-2.4.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\springframework\boot\spring-boot-starter-web\3.5.3\spring-boot-starter-web-3.5.3.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\springframework\boot\spring-boot-starter-json\3.5.3\spring-boot-starter-json-3.5.3.jar;D:\soft\apache-maven-3.8.8\mvn_resp\com\fasterxml\jackson\core\jackson-databind\2.19.1\jackson-databind-2.19.1.jar;D:\soft\apache-maven-3.8.8\mvn_resp\com\fasterxml\jackson\core\jackson-annotations\2.19.1\jackson-annotations-2.19.1.jar;D:\soft\apache-maven-3.8.8\mvn_resp\com\fasterxml\jackson\core\jackson-core\2.19.1\jackson-core-2.19.1.jar;D:\soft\apache-maven-3.8.8\mvn_resp\com\fasterxml\jackson\datatype\jackson-datatype-jdk8\2.19.1\jackson-datatype-jdk8-2.19.1.jar;D:\soft\apache-maven-3.8.8\mvn_resp\com\fasterxml\jackson\datatype\jackson-datatype-jsr310\2.19.1\jackson-datatype-jsr310-2.19.1.jar;D:\soft\apache-maven-3.8.8\mvn_resp\com\fasterxml\jackson\module\jackson-module-parameter-names\2.19.1\jackson-module-parameter-names-2.19.1.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\springframework\boot\spring-boot-starter-tomcat\3.5.3\spring-boot-starter-tomcat-3.5.3.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\apache\tomcat\embed\tomcat-embed-core\10.1.42\tomcat-embed-core-10.1.42.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\apache\tomcat\embed\tomcat-embed-el\10.1.42\tomcat-embed-el-10.1.42.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\apache\tomcat\embed\tomcat-embed-websocket\10.1.42\tomcat-embed-websocket-10.1.42.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\springframework\spring-web\6.2.8\spring-web-6.2.8.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\springframework\spring-beans\6.2.8\spring-beans-6.2.8.jar;D:\soft\apache-maven-3.8.8\mvn_resp\io\micrometer\micrometer-observation\1.15.1\micrometer-observation-1.15.1.jar;D:\soft\apache-maven-3.8.8\mvn_resp\io\micrometer\micrometer-commons\1.15.1\micrometer-commons-1.15.1.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\springframework\spring-webmvc\6.2.8\spring-webmvc-6.2.8.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\springframework\spring-aop\6.2.8\spring-aop-6.2.8.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\springframework\spring-expression\6.2.8\spring-expression-6.2.8.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\slf4j\slf4j-api\2.0.17\slf4j-api-2.0.17.jar;D:\soft\apache-maven-3.8.8\mvn_resp\jakarta\xml\bind\jakarta.xml.bind-api\4.0.2\jakarta.xml.bind-api-4.0.2.jar;D:\soft\apache-maven-3.8.8\mvn_resp\jakarta\activation\jakarta.activation-api\2.1.3\jakarta.activation-api-2.1.3.jar;D:\soft\apache-maven-3.8.8\mvn_resp\net\bytebuddy\byte-buddy\1.17.6\byte-buddy-1.17.6.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\springframework\boot\spring-boot-starter-data-jpa\3.5.3\spring-boot-starter-data-jpa-3.5.3.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\springframework\boot\spring-boot-starter-jdbc\3.5.3\spring-boot-starter-jdbc-3.5.3.jar;D:\soft\apache-maven-3.8.8\mvn_resp\com\zaxxer\HikariCP\6.3.0\HikariCP-6.3.0.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\springframework\spring-jdbc\6.2.8\spring-jdbc-6.2.8.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\hibernate\orm\hibernate-core\6.6.18.Final\hibernate-core-6.6.18.Final.jar;D:\soft\apache-maven-3.8.8\mvn_resp\jakarta\persistence\jakarta.persistence-api\3.1.0\jakarta.persistence-api-3.1.0.jar;D:\soft\apache-maven-3.8.8\mvn_resp\jakarta\transaction\jakarta.transaction-api\2.0.1\jakarta.transaction-api-2.0.1.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\jboss\logging\jboss-logging\3.6.1.Final\jboss-logging-3.6.1.Final.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\hibernate\common\hibernate-commons-annotations\7.0.3.Final\hibernate-commons-annotations-7.0.3.Final.jar;D:\soft\apache-maven-3.8.8\mvn_resp\io\smallrye\jandex\3.2.0\jandex-3.2.0.jar;D:\soft\apache-maven-3.8.8\mvn_resp\com\fasterxml\classmate\1.7.0\classmate-1.7.0.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\glassfish\jaxb\jaxb-runtime\4.0.5\jaxb-runtime-4.0.5.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\glassfish\jaxb\jaxb-core\4.0.5\jaxb-core-4.0.5.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\eclipse\angus\angus-activation\2.0.2\angus-activation-2.0.2.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\glassfish\jaxb\txw2\4.0.5\txw2-4.0.5.jar;D:\soft\apache-maven-3.8.8\mvn_resp\com\sun\istack\istack-commons-runtime\4.1.2\istack-commons-runtime-4.1.2.jar;D:\soft\apache-maven-3.8.8\mvn_resp\jakarta\inject\jakarta.inject-api\2.0.1\jakarta.inject-api-2.0.1.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\antlr\antlr4-runtime\4.13.0\antlr4-runtime-4.13.0.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\springframework\data\spring-data-jpa\3.5.1\spring-data-jpa-3.5.1.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\springframework\data\spring-data-commons\3.5.1\spring-data-commons-3.5.1.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\springframework\spring-orm\6.2.8\spring-orm-6.2.8.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\springframework\spring-tx\6.2.8\spring-tx-6.2.8.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\springframework\spring-aspects\6.2.8\spring-aspects-6.2.8.jar;D:\soft\apache-maven-3.8.8\mvn_resp\org\aspectj\aspectjweaver\1.9.24\aspectjweaver-1.9.24.jar;D:\soft\apache-maven-3.8.8\mvn_resp\mysql\mysql-connector-java\8.0.28\mysql-connector-java-8.0.28.jar;D:\soft\apache-maven-3.8.8\mvn_resp\com\google\protobuf\protobuf-java\3.11.4\protobuf-java-3.11.4.jar com.example.user.UserApplication . ____ _ __ _ _ /\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \ ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \ \\/ ___)| |_)| | | | | || (_| | ) ) ) ) ' |____| .__|_| |_|_| |_\__, | / / / / =========|_|==============|___/=/_/_/_/ :: Spring Boot :: (v3.5.3) 2025-07-06T20:45:06.853+08:00 INFO 11980 --- [user] [ main] com.example.user.UserApplication : Starting UserApplication using Java 18.0.2 with PID 11980 (D:\javacode\user\target\classes started by admin in D:\javacode\user) 2025-07-06T20:45:06.858+08:00 INFO 11980 --- [user] [ main] com.example.user.UserApplication : No active profile set, falling back to 1 default profile: "default" 2025-07-06T20:45:07.934+08:00 INFO 11980 --- [user] [ main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data JPA repositories in DEFAULT mode. 2025-07-06T20:45:07.966+08:00 INFO 11980 --- [user] [ main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 18 ms. Found 0 JPA repository interfaces. 2025-07-06T20:45:08.675+08:00 INFO 11980 --- [user] [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port 8080 (http) 2025-07-06T20:45:08.701+08:00 INFO 11980 --- [user] [ main] o.apache.catalina.core.StandardService : Starting service [Tomcat] 2025-07-06T20:45:08.701+08:00 INFO 11980 --- [user] [ main] o.apache.catalina.core.StandardEngine : Starting Servlet engine: [Apache Tomcat/10.1.42] 2025-07-06T20:45:08.781+08:00 INFO 11980 --- [user] [ main] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring embedded WebApplicationContext 2025-07-06T20:45:08.782+08:00 INFO 11980 --- [user] [ main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 1837 ms 2025-07-06T20:45:09.112+08:00 INFO 11980 --- [user] [ main] o.hibernate.jpa.internal.util.LogHelper : HHH000204: Processing PersistenceUnitInfo [name: default] 2025-07-06T20:45:09.202+08:00 INFO 11980 --- [user] [ main] org.hibernate.Version : HHH000412: Hibernate ORM core version 6.6.18.Final 2025-07-06T20:45:09.259+08:00 INFO 11980 --- [user] [ main] o.h.c.internal.RegionFactoryInitiator : HHH000026: Second-level cache disabled 2025-07-06T20:45:09.744+08:00 INFO 11980 --- [user] [ main] o.s.o.j.p.SpringPersistenceUnitInfo : No LoadTimeWeaver setup: ignoring JPA class transformer 2025-07-06T20:45:09.799+08:00 INFO 11980 --- [user] [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Starting... 2025-07-06T20:45:10.051+08:00 INFO 11980 --- [user] [ main] com.zaxxer.hikari.pool.HikariPool : HikariPool-1 - Added connection com.mysql.cj.jdbc.ConnectionImpl@4fbb1144 2025-07-06T20:45:10.055+08:00 INFO 11980 --- [user] [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Start completed. 2025-07-06T20:45:10.093+08:00 WARN 11980 --- [user] [ main] org.hibernate.orm.deprecation : HHH90000025: MySQL8Dialect does not need to be specified explicitly using 'hibernate.dialect' (remove the property setting and it will be selected by default) 2025-07-06T20:45:10.095+08:00 WARN 11980 --- [user] [ main] org.hibernate.orm.deprecation : HHH90000026: MySQL8Dialect has been deprecated; use org.hibernate.dialect.MySQLDialect instead 2025-07-06T20:45:10.131+08:00 INFO 11980 --- [user] [ main] org.hibernate.orm.connections.pooling : HHH10001005: Database info: Database JDBC URL [Connecting through datasource 'HikariDataSource (HikariPool-1)'] Database driver: undefined/unknown Database version: 8.0 Autocommit mode: undefined/unknown Isolation level: undefined/unknown Minimum pool size: undefined/unknown Maximum pool size: undefined/unknown 2025-07-06T20:45:10.794+08:00 INFO 11980 --- [user] [ main] o.h.e.t.j.p.i.JtaPlatformInitiator : HHH000489: No JTA platform available (set 'hibernate.transaction.jta.platform' to enable JTA platform integration) 2025-07-06T20:45:10.803+08:00 INFO 11980 --- [user] [ main] j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory for persistence unit 'default' 2025-07-06T20:45:10.862+08:00 WARN 11980 --- [user] [ main] JpaBaseConfiguration$JpaWebConfiguration : spring.jpa.open-in-view is enabled by default. Therefore, database queries may be performed during view rendering. Explicitly configure spring.jpa.open-in-view to disable this warning 2025-07-06T20:45:11.532+08:00 INFO 11980 --- [user] [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat started on port 8080 (http) with context path '/' 2025-07-06T20:45:11.545+08:00 INFO 11980 --- [user] [ main] com.example.user.UserApplication : Started UserApplication in 5.52 seconds (process running for 6.562) 2025-07-06T20:45:55.912+08:00 INFO 11980 --- [user] [nio-8080-exec-1] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring DispatcherServlet 'dispatcherServlet' 2025-07-06T20:45:55.913+08:00 INFO 11980 --- [user] [nio-8080-exec-1] o.s.web.servlet.DispatcherServlet : Initializing Servlet 'dispatcherServlet' 2025-07-06T20:45:55.916+08:00 INFO 11980 --- [user] [nio-8080-exec-1] o.s.web.servlet.DispatcherServlet : Completed initialization in 3 ms Whitelabel Error Page This application has no explicit mapping for /error, so you are seeing this as a fallback. Sun Jul 06 20:46:26 CST 2025 There was an unexpected error (type=Not Found, status=404).
07-07
在 Spring Boot 应用中,Whitelabel Error Page 是一个默认的错误页面,当应用程序未定义自定义错误页面时显示。此页面通常在未正确配置错误处理机制时出现,尤其是 `/error` 或 `/error500` 等路径未被显式映射。要解决该问题,需要配置自定义错误页面,并确保这些路径被正确映射。 一种解决方案是通过实现 `ErrorController` 接口并定义 `/error` 路径的映射,以提供自定义的错误页面。以下是一个示例实现: ```java import org.springframework.boot.web.servlet.error.ErrorController; import org.springframework.stereotype.Controller; import org.springframework.web.bind.annotation.RequestMapping; import javax.servlet.RequestDispatcher; import javax.servlet.http.HttpServletRequest; @Controller public class CustomErrorController implements ErrorController { @RequestMapping("/error") public String handleError(HttpServletRequest request) { Object status = request.getAttribute(RequestDispatcher.ERROR_STATUS_CODE); if (status != null) { Integer statusCode = Integer.valueOf(status.toString()); if (statusCode == 500) { return "error500"; // 返回 error500 页面 } } return "error"; // 默认错误页面 } @Override public String getErrorPath() { return "/error"; } } ``` 此外,还可以通过配置 `application.properties` 文件来禁用 Whitelabel 错误页面,同时启用自定义错误页面: ``` spring.mvc.throw-exception-if-no-handler-found=false spring.boot.enable-logging=false spring.thymeleaf.cache=false ``` 在 `resources/templates` 目录下创建 `error.html` 和 `error500.html` 页面,以提供友好的错误提示信息。例如: ```html <!DOCTYPE html> <html xmlns:th="http://www.thymeleaf.org"> <head> <title>Error</title> </head> <body> <h1>Error Occurred</h1> <p th:text="${error}">An unexpected error occurred.</p> </body> </html> ``` 对于 `/error500` 的显式映射,可以通过添加一个额外的 `@RequestMapping` 来处理: ```java @RequestMapping("/error500") public String handleInternalServerError() { return "error500"; } ``` 通过上述配置,Whitelabel Error Page 将不再显示,并且 `/error500` 路径将被正确映射到自定义的错误页面[^1]。 ### 相关问题 1. 如何在 Spring Boot 中自定义 404 错误页面? 2. 如何通过全局异常处理器(@ControllerAdvice)处理错误? 3. Spring Boot 中的 Thymeleaf 模板如何与错误页面集成? 4. 如何在 Spring Boot 应用中启用详细的错误日志? 5. 如何测试 Spring Boot 应用的错误页面配置?
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值