关于部署项目到tomcat,报FAIL - Application at context path /JDYProject could not be started

本文分享了一次将项目部署到Linux服务器上Tomcat的webapps目录后遇到404错误的解决过程。通过查看日志,发现是由于本地开发环境的JDK版本(1.8)与服务器JDK版本(1.7)不一致导致的Unsupported major.minor version错误。文章强调了版本一致性的重要性,并提醒开发者在遇到问题时,直接查看日志可以更高效地定位问题。

最近将打包好的项目部署到linux服务器上的tomcat的webapps目录下,然后访问项目index.jsp,发现一直报404错误。

检查了项目,发现项目在本地IDE下,运行正常。然后把目光聚集于tomcat上。

打开tomcat服务器首页,然后点击进入Manager App,手动打开项目。

结果发现,项目Running状态为false。所以尝试了一下手动Start项目。

结果:

发现了Message:

FAIL - Application at context path /JDYProject could not be started

然后百度,百度再百度。一直没有百度到自己想要的结果。

于是去看来tomcat的启动目录的日志,这下转机就来了。

进入tomcat安装目录,然后进入logs目录:

然后查看最新的catalina日志:

vi catalina.2018-07-31.log

终于看到了报错信息了:

报的Unsupported major.minor version 52.0 错误。

原来,都是版本不对应惹的祸啊。。。

我linux服务器jdk版本为1.7,然而开发项目的本地环境的jdk版本是1.8,在部署到jdk版本为1.7的linux服务器上时,版本不一致,自然会报错。所以,这里给自己提了个醒,别为了偷懒,胡乱用版本不一致的环境,否则会出现很多额外的麻烦和工作量,还有就是开发项目或部署项目时,报错不可怕,最可怕的就是没有方向的百度,这样时间成本太高了,最有效的就是直接查看日志,精确查找到错误的详细信息。

Application run failed java.lang.IllegD:\module\java17\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 "-Dmanagement.endpoints.jmx.exposure.include=*" "-javaagent:D:\anp\IntelliJ IDEA 2024.3\lib\idea_rt.jar=5929:D:\anp\IntelliJ IDEA 2024.3\bin" -Dfile.encoding=UTF-8 -classpath D:\1\lingyidianke\lingyidianke\lingyidianke-leadnews-service\lingyidianke-leadnews-user\target\classes;D:\1\lingyidianke-repository\org\springframework\cloud\spring-cloud-starter-bootstrap\4.1.4\spring-cloud-starter-bootstrap-4.1.4.jar;D:\1\lingyidianke-repository\org\springframework\cloud\spring-cloud-starter\4.1.4\spring-cloud-starter-4.1.4.jar;D:\1\lingyidianke-repository\org\springframework\security\spring-security-rsa\1.1.3\spring-security-rsa-1.1.3.jar;D:\1\lingyidianke-repository\org\bouncycastle\bcprov-jdk18on\1.78\bcprov-jdk18on-1.78.jar;D:\1\lingyidianke-repository\org\projectlombok\lombok\1.18.30\lombok-1.18.30.jar;D:\1\lingyidianke\lingyidianke\lingyidianke-leadnews-model\target\classes;D:\1\lingyidianke-repository\com\alibaba\fastjson\1.2.58\fastjson-1.2.58.jar;D:\1\lingyidianke-repository\com\mysql\mysql-connector-j\8.0.33\mysql-connector-j-8.0.33.jar;D:\1\lingyidianke-repository\com\google\protobuf\protobuf-java\3.21.9\protobuf-java-3.21.9.jar;D:\1\lingyidianke-repository\org\apache\commons\commons-lang3\3.14.0\commons-lang3-3.14.0.jar;D:\1\lingyidianke-repository\com\baomidou\mybatis-plus-spring-boot3-starter\3.5.7\mybatis-plus-spring-boot3-starter-3.5.7.jar;D:\1\lingyidianke-repository\com\baomidou\mybatis-plus\3.5.7\mybatis-plus-3.5.7.jar;D:\1\lingyidianke-repository\org\mybatis\mybatis-spring\3.0.3\mybatis-spring-3.0.3.jar;D:\1\lingyidianke-repository\com\baomidou\mybatis-plus-spring-boot-autoconfigure\3.5.7\mybatis-plus-spring-boot-autoconfigure-3.5.7.jar;D:\1\lingyidianke-repository\org\springframework\boot\spring-boot-starter-jdbc\3.3.4\spring-boot-starter-jdbc-3.3.4.jar;D:\1\lingyidianke-repository\com\zaxxer\HikariCP\5.1.0\HikariCP-5.1.0.jar;D:\1\lingyidianke-repository\org\springframework\spring-jdbc\6.1.13\spring-jdbc-6.1.13.jar;D:\1\lingyidianke-repository\org\springframework\spring-tx\6.1.13\spring-tx-6.1.13.jar;D:\1\lingyidianke-repository\io\swagger\swagger-annotations\1.5.22\swagger-annotations-1.5.22.jar;D:\1\lingyidianke-repository\ch\qos\logback\logback-classic\1.4.11\logback-classic-1.4.11.jar;D:\1\lingyidianke-repository\ch\qos\logback\logback-core\1.5.8\logback-core-1.5.8.jar;D:\1\lingyidianke-repository\org\slf4j\slf4j-api\2.0.16\slf4j-api-2.0.16.jar;D:\1\lingyidianke-repository\com\baomidou\mybatis-plus-extension\3.5.7\mybatis-plus-extension-3.5.7.jar;D:\1\lingyidianke-repository\com\baomidou\mybatis-plus-core\3.5.7\mybatis-plus-core-3.5.7.jar;D:\1\lingyidianke-repository\com\baomidou\mybatis-plus-annotation\3.5.7\mybatis-plus-annotation-3.5.7.jar;D:\1\lingyidianke-repository\com\github\jsqlparser\jsqlparser\4.9\jsqlparser-4.9.jar;D:\1\lingyidianke-repository\org\mybatis\mybatis\3.5.16\mybatis-3.5.16.jar;D:\1\lingyidianke\lingyidianke\lingyidianke-leadnews-feign-api\target\classes;D:\1\lingyidianke\lingyidianke\lingyidianke-leadnews-common\target\classes;D:\1\lingyidianke-repository\com\github\xiaoymin\knife4j-spring-boot-starter\3.0.3\knife4j-spring-boot-starter-3.0.3.jar;D:\1\lingyidianke-repository\com\github\xiaoymin\knife4j-spring-boot-autoconfigure\3.0.3\knife4j-spring-boot-autoconfigure-3.0.3.jar;D:\1\lingyidianke-repository\com\github\xiaoymin\knife4j-spring\3.0.3\knife4j-spring-3.0.3.jar;D:\1\lingyidianke-repository\com\github\xiaoymin\knife4j-annotations\3.0.3\knife4j-annotations-3.0.3.jar;D:\1\lingyidianke-repository\io\swagger\core\v3\swagger-annotations\2.1.2\swagger-annotations-2.1.2.jar;D:\1\lingyidianke-repository\com\github\xiaoymin\knife4j-core\3.0.3\knife4j-core-3.0.3.jar;D:\1\lingyidianke-repository\org\javassist\javassist\3.25.0-GA\javassist-3.25.0-GA.jar;D:\1\lingyidianke-repository\io\springfox\springfox-swagger2\3.0.0\springfox-swagger2-3.0.0.jar;D:\1\lingyidianke-repository\io\springfox\springfox-spi\3.0.0\springfox-spi-3.0.0.jar;D:\1\lingyidianke-repository\io\springfox\springfox-schema\3.0.0\springfox-schema-3.0.0.jar;D:\1\lingyidianke-repository\io\springfox\springfox-swagger-common\3.0.0\springfox-swagger-common-3.0.0.jar;D:\1\lingyidianke-repository\io\springfox\springfox-spring-web\3.0.0\springfox-spring-web-3.0.0.jar;D:\1\lingyidianke-repository\io\github\classgraph\classgraph\4.8.83\classgraph-4.8.83.jar;D:\1\lingyidianke-repository\io\springfox\springfox-spring-webflux\3.0.0\springfox-spring-webflux-3.0.0.jar;D:\1\lingyidianke-repository\org\mapstruct\mapstruct\1.3.1.Final\mapstruct-1.3.1.Final.jar;D:\1\lingyidianke-repository\io\springfox\springfox-spring-webmvc\3.0.0\springfox-spring-webmvc-3.0.0.jar;D:\1\lingyidianke-repository\io\springfox\springfox-core\3.0.0\springfox-core-3.0.0.jar;D:\1\lingyidianke-repository\io\springfox\springfox-oas\3.0.0\springfox-oas-3.0.0.jar;D:\1\lingyidianke-repository\io\swagger\core\v3\swagger-models\2.1.2\swagger-models-2.1.2.jar;D:\1\lingyidianke-repository\io\springfox\springfox-bean-validators\3.0.0\springfox-bean-validators-3.0.0.jar;D:\1\lingyidianke-repository\io\swagger\swagger-models\1.5.22\swagger-models-1.5.22.jar;D:\1\lingyidianke-repository\io\swagger\swagger-core\1.5.22\swagger-core-1.5.22.jar;D:\1\lingyidianke-repository\com\fasterxml\jackson\dataformat\jackson-dataformat-yaml\2.17.2\jackson-dataformat-yaml-2.17.2.jar;D:\1\lingyidianke-repository\com\google\guava\guava\27.0.1-android\guava-27.0.1-android.jar;D:\1\lingyidianke-repository\com\google\guava\failureaccess\1.0.1\failureaccess-1.0.1.jar;D:\1\lingyidianke-repository\com\google\guava\listenablefuture\9999.0-empty-to-avoid-conflict-with-guava\listenablefuture-9999.0-empty-to-avoid-conflict-with-guava.jar;D:\1\lingyidianke-repository\com\google\code\findbugs\jsr305\3.0.2\jsr305-3.0.2.jar;D:\1\lingyidianke-repository\org\checkerframework\checker-compat-qual\2.5.2\checker-compat-qual-2.5.2.jar;D:\1\lingyidianke-repository\com\google\errorprone\error_prone_annotations\2.2.0\error_prone_annotations-2.2.0.jar;D:\1\lingyidianke-repository\com\google\j2objc\j2objc-annotations\1.1\j2objc-annotations-1.1.jar;D:\1\lingyidianke-repository\org\codehaus\mojo\animal-sniffer-annotations\1.17\animal-sniffer-annotations-1.17.jar;D:\1\lingyidianke-repository\javax\validation\validation-api\1.1.0.Final\validation-api-1.1.0.Final.jar;D:\1\lingyidianke-repository\io\springfox\springfox-boot-starter\3.0.0\springfox-boot-starter-3.0.0.jar;D:\1\lingyidianke-repository\io\springfox\springfox-data-rest\3.0.0\springfox-data-rest-3.0.0.jar;D:\1\lingyidianke-repository\com\fasterxml\classmate\1.7.0\classmate-1.7.0.jar;D:\1\lingyidianke-repository\org\springframework\plugin\spring-plugin-core\2.0.0.RELEASE\spring-plugin-core-2.0.0.RELEASE.jar;D:\1\lingyidianke-repository\org\springframework\plugin\spring-plugin-metadata\2.0.0.RELEASE\spring-plugin-metadata-2.0.0.RELEASE.jar;D:\1\lingyidianke-repository\com\github\xiaoymin\knife4j-spring-ui\3.0.3\knife4j-spring-ui-3.0.3.jar;D:\1\lingyidianke\lingyidianke\lingyidianke-leadnews-utils\target\classes;D:\1\lingyidianke-repository\io\jsonwebtoken\jjwt\0.9.1\jjwt-0.9.1.jar;D:\1\lingyidianke-repository\org\springframework\boot\spring-boot-starter\3.3.4\spring-boot-starter-3.3.4.jar;D:\1\lingyidianke-repository\org\springframework\boot\spring-boot\3.3.4\spring-boot-3.3.4.jar;D:\1\lingyidianke-repository\org\springframework\spring-context\6.1.13\spring-context-6.1.13.jar;D:\1\lingyidianke-repository\org\springframework\boot\spring-boot-autoconfigure\3.3.4\spring-boot-autoconfigure-3.3.4.jar;D:\1\lingyidianke-repository\org\springframework\boot\spring-boot-starter-logging\3.3.4\spring-boot-starter-logging-3.3.4.jar;D:\1\lingyidianke-repository\org\apache\logging\log4j\log4j-to-slf4j\2.23.1\log4j-to-slf4j-2.23.1.jar;D:\1\lingyidianke-repository\org\apache\logging\log4j\log4j-api\2.23.1\log4j-api-2.23.1.jar;D:\1\lingyidianke-repository\org\slf4j\jul-to-slf4j\2.0.16\jul-to-slf4j-2.0.16.jar;D:\1\lingyidianke-repository\jakarta\annotation\jakarta.annotation-api\2.1.1\jakarta.annotation-api-2.1.1.jar;D:\1\lingyidianke-repository\org\springframework\spring-core\6.1.13\spring-core-6.1.13.jar;D:\1\lingyidianke-repository\org\springframework\spring-jcl\6.1.13\spring-jcl-6.1.13.jar;D:\1\lingyidianke-repository\org\yaml\snakeyaml\2.2\snakeyaml-2.2.jar;D:\1\lingyidianke-repository\org\springframework\boot\spring-boot-starter-web\3.3.4\spring-boot-starter-web-3.3.4.jar;D:\1\lingyidianke-repository\org\springframework\boot\spring-boot-starter-json\3.3.4\spring-boot-starter-json-3.3.4.jar;D:\1\lingyidianke-repository\com\fasterxml\jackson\datatype\jackson-datatype-jdk8\2.17.2\jackson-datatype-jdk8-2.17.2.jar;D:\1\lingyidianke-repository\com\fasterxml\jackson\datatype\jackson-datatype-jsr310\2.17.2\jackson-datatype-jsr310-2.17.2.jar;D:\1\lingyidianke-repository\com\fasterxml\jackson\module\jackson-module-parameter-names\2.17.2\jackson-module-parameter-names-2.17.2.jar;D:\1\lingyidianke-repository\org\springframework\boot\spring-boot-starter-tomcat\3.3.4\spring-boot-starter-tomcat-3.3.4.jar;D:\1\lingyidianke-repository\org\apache\tomcat\embed\tomcat-embed-core\10.1.30\tomcat-embed-core-10.1.30.jar;D:\1\lingyidianke-repository\org\apache\tomcat\embed\tomcat-embed-el\10.1.30\tomcat-embed-el-10.1.30.jar;D:\1\lingyidianke-repository\org\apache\tomcat\embed\tomcat-embed-websocket\10.1.30\tomcat-embed-websocket-10.1.30.jar;D:\1\lingyidianke-repository\org\springframework\spring-web\6.1.13\spring-web-6.1.13.jar;D:\1\lingyidianke-repository\org\springframework\spring-beans\6.1.13\spring-beans-6.1.13.jar;D:\1\lingyidianke-repository\io\micrometer\micrometer-observation\1.13.4\micrometer-observation-1.13.4.jar;D:\1\lingyidianke-repository\io\micrometer\micrometer-commons\1.13.4\micrometer-commons-1.13.4.jar;D:\1\lingyidianke-repository\org\springframework\spring-webmvc\6.1.13\spring-webmvc-6.1.13.jar;D:\1\lingyidianke-repository\org\springframework\spring-aop\6.1.13\spring-aop-6.1.13.jar;D:\1\lingyidianke-repository\org\springframework\spring-expression\6.1.13\spring-expression-6.1.13.jar;D:\1\lingyidianke-repository\net\bytebuddy\byte-buddy\1.14.19\byte-buddy-1.14.19.jar;D:\1\lingyidianke-repository\com\alibaba\nacos\nacos-client\2.2.3\nacos-client-2.2.3.jar;D:\1\lingyidianke-repository\com\alibaba\nacos\nacos-auth-plugin\2.2.3\nacos-auth-plugin-2.2.3.jar;D:\1\lingyidianke-repository\com\alibaba\nacos\nacos-encryption-plugin\2.2.3\nacos-encryption-plugin-2.2.3.jar;D:\1\lingyidianke-repository\commons-codec\commons-codec\1.16.1\commons-codec-1.16.1.jar;D:\1\lingyidianke-repository\com\fasterxml\jackson\core\jackson-core\2.17.2\jackson-core-2.17.2.jar;D:\1\lingyidianke-repository\com\fasterxml\jackson\core\jackson-databind\2.17.2\jackson-databind-2.17.2.jar;D:\1\lingyidianke-repository\com\fasterxml\jackson\core\jackson-annotations\2.17.2\jackson-annotations-2.17.2.jar;D:\1\lingyidianke-repository\org\apache\httpcomponents\httpasyncclient\4.1.5\httpasyncclient-4.1.5.jar;D:\1\lingyidianke-repository\org\apache\httpcomponents\httpcore\4.4.16\httpcore-4.4.16.jar;D:\1\lingyidianke-repository\org\apache\httpcomponents\httpcore-nio\4.4.16\httpcore-nio-4.4.16.jar;D:\1\lingyidianke-repository\org\apache\httpcomponents\httpclient\4.5.13\httpclient-4.5.13.jar;D:\1\lingyidianke-repository\io\prometheus\simpleclient\0.16.0\simpleclient-0.16.0.jar;D:\1\lingyidianke-repository\io\prometheus\simpleclient_tracer_otel\0.16.0\simpleclient_tracer_otel-0.16.0.jar;D:\1\lingyidianke-repository\io\prometheus\simpleclient_tracer_common\0.16.0\simpleclient_tracer_common-0.16.0.jar;D:\1\lingyidianke-repository\io\prometheus\simpleclient_tracer_otel_agent\0.16.0\simpleclient_tracer_otel_agent-0.16.0.jar;D:\1\lingyidianke-repository\com\alibaba\cloud\spring-cloud-starter-alibaba-nacos-discovery\2023.0.3.2\spring-cloud-starter-alibaba-nacos-discovery-2023.0.3.2.jar;D:\1\lingyidianke-repository\com\alibaba\cloud\spring-cloud-alibaba-commons\2023.0.3.2\spring-cloud-alibaba-commons-2023.0.3.2.jar;D:\1\lingyidianke-repository\org\springframework\cloud\spring-cloud-commons\4.1.4\spring-cloud-commons-4.1.4.jar;D:\1\lingyidianke-repository\org\springframework\security\spring-security-crypto\6.3.3\spring-security-crypto-6.3.3.jar;D:\1\lingyidianke-repository\org\springframework\cloud\spring-cloud-context\4.1.4\spring-cloud-context-4.1.4.jar;D:\1\lingyidianke-repository\com\alibaba\cloud\spring-cloud-starter-alibaba-nacos-config\2023.0.3.2\spring-cloud-starter-alibaba-nacos-config-2023.0.3.2.jar;D:\1\lingyidianke-repository\com\alibaba\cloud\spring-alibaba-nacos-config\2023.0.3.2\spring-alibaba-nacos-config-2023.0.3.2.jar com.lingyidianke.service.user.LingyidiankeLeadnewsUserApplication Application starting... 2025-07-01 13:37:15.810 [main] WARN c.a.n.client.logging.NacosLogging - Load Logback Configuration of Nacos fail, message: Could not initialize Logback Nacos logging from classpath:nacos-logback.xml 2025-07-01 13:37:16.101 [main] WARN c.a.n.client.logging.NacosLogging - Load Logback Configuration of Nacos fail, message: Could not initialize Logback Nacos logging from classpath:nacos-logback.xml 2025-07-01 13:37:17.859 [main] WARN c.a.n.client.logging.NacosLogging - Load Logback Configuration of Nacos fail, message: Could not initialize Logback Nacos logging from classpath:nacos-logback.xml . ____ _ __ _ _ /\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \ ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \ \\/ ___)| |_)| | | | | || (_| | ) ) ) ) ' |____| .__|_| |_|_| |_\__, | / / / / =========|_|==============|___/=/_/_/_/ :: Spring Boot :: (v3.3.4) 2025-07-01 13:37:17.916 [main] WARN c.a.n.client.logging.NacosLogging - Load Logback Configuration of Nacos fail, message: Could not initialize Logback Nacos logging from classpath:nacos-logback.xml 2025-07-01 13:37:17.919 [main] INFO c.l.s.u.LingyidiankeLeadnewsUserApplication - No active profile set, falling back to 1 default profile: "default" 2025-07-01 13:37:20.339 [main] DEBUG o.apache.ibatis.logging.LogFactory - Logging initialized using 'class org.apache.ibatis.logging.slf4j.Slf4jImpl' adapter. 2025-07-01 13:37:20.344 [main] DEBUG o.m.s.mapper.ClassPathMapperScanner - Identified candidate component class: file [D:\1\lingyidianke\lingyidianke\lingyidianke-leadnews-service\lingyidianke-leadnews-user\target\classes\com\lingyidianke\service\user\mapper\ApUserMapper.class] 2025-07-01 13:37:20.345 [main] DEBUG o.m.s.mapper.ClassPathMapperScanner - Creating MapperFactoryBean with name 'apUserMapper' and 'com.lingyidianke.service.user.mapper.ApUserMapper' mapperInterface 2025-07-01 13:37:20.351 [main] DEBUG o.m.s.mapper.ClassPathMapperScanner - Enabling autowire by type for MapperFactoryBean with name 'apUserMapper'. 2025-07-01 13:37:20.628 [main] INFO o.s.cloud.context.scope.GenericScope - BeanFactory id=3c43dc0a-4512-3230-88b9-a854c1cec355 2025-07-01 13:37:20.730 [main] WARN o.s.c.s.PostProcessorRegistrationDelegate$BeanPostProcessorChecker - Bean 'com.alibaba.cloud.nacos.NacosConfigAutoConfiguration' of type [com.alibaba.cloud.nacos.NacosConfigAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). The currently created BeanPostProcessor [nacosAnnotationProcessor] is declared through a non-static factory method on that class; consider declaring it as static instead. 2025-07-01 13:37:21.365 [main] INFO o.s.b.w.e.tomcat.TomcatWebServer - Tomcat initialized with port 51801 (http) 2025-07-01 13:37:21.389 [main] INFO o.a.coyote.http11.Http11NioProtocol - Initializing ProtocolHandler ["http-nio-51801"] 2025-07-01 13:37:21.397 [main] INFO o.a.catalina.core.StandardService - Starting service [Tomcat] 2025-07-01 13:37:21.399 [main] INFO o.a.catalina.core.StandardEngine - Starting Servlet engine: [Apache Tomcat/10.1.30] 2025-07-01 13:37:21.577 [main] INFO o.a.c.c.C.[Tomcat].[localhost].[/] - Initializing Spring embedded WebApplicationContext 2025-07-01 13:37:21.578 [main] INFO o.s.b.w.s.c.ServletWebServerApplicationContext - Root WebApplicationContext: initialization completed in 3618 ms 2025-07-01 13:37:21.923 [main] DEBUG c.b.m.e.s.MybatisSqlSessionFactoryBean - Registered plugin: 'MybatisPlusInterceptor{interceptors=[PaginationInnerInterceptor(logger=org.apache.ibatis.logging.slf4j.Slf4jImpl@5b1efaaf, overflow=false, maxLimit=null, dbType=MYSQL, dialect=null, optimizeJoin=true), com.baomidou.mybatisplus.extension.plugins.inner.OptimisticLockerInnerInterceptor@27585351]}' 2025-07-01 13:37:21.926 [main] DEBUG c.b.m.e.s.MybatisSqlSessionFactoryBean - Property 'mapperLocations' was not specified. 2025-07-01 13:37:22.330 [main] DEBUG c.b.m.core.toolkit.Sequence - Get /192.168.96.1 network interface 2025-07-01 13:37:22.369 [main] DEBUG c.b.m.core.toolkit.Sequence - Get network interface info: name:eth7 (VMware Virtual Ethernet Adapter for VMnet0) 2025-07-01 13:37:22.393 [main] DEBUG c.b.m.core.toolkit.Sequence - Initialization Sequence datacenterId:0 workerId:1 _ _ |_ _ _|_. ___ _ | _ | | |\/|_)(_| | |_\ |_)||_|_\ / | 3.5.7 2025-07-01 13:37:23.099 [main] DEBUG _.s.w.s.HandlerMapping.Mappings - c.l.s.u.c.ApUserLoginController: {POST [/api/v1/login/login_auth]}: login(LoginDto) 2025-07-01 13:37:23.107 [main] DEBUG _.s.w.s.HandlerMapping.Mappings - o.s.b.a.w.s.e.BasicErrorController: { [/error]}: error(HttpServletRequest) { [/error], produces [text/html]}: errorHtml(HttpServletRequest,HttpServletResponse) 2025-07-01 13:37:23.128 [main] DEBUG _.s.w.s.HandlerMapping.Mappings - 'beanNameHandlerMapping' {} 2025-07-01 13:37:23.286 [main] DEBUG _.s.w.s.HandlerMapping.Mappings - 'resourceHandlerMapping' {/webjars/**=ResourceHttpRequestHandler [classpath [META-INF/resources/webjars/]], /**=ResourceHttpRequestHandler [classpath [META-INF/resources/], classpath [resources/], classpath [static/], classpath [public/], ServletContext [/]]} 2025-07-01 13:37:23.526 [main] WARN c.a.n.client.logging.NacosLogging - Load Logback Configuration of Nacos fail, message: Could not initialize Logback Nacos logging from classpath:nacos-logback.xml 2025-07-01 13:37:23.530 [main] INFO c.a.nacos.client.utils.ParamUtil - [settings] [req-serv] nacos-server port:8848 2025-07-01 13:37:23.530 [main] INFO c.a.nacos.client.utils.ParamUtil - [settings] [http-client] connect timeout:1000 2025-07-01 13:37:23.535 [main] INFO c.a.nacos.client.utils.ParamUtil - PER_TASK_CONFIG_SIZE: 3000.0 2025-07-01 13:37:23.615 [main] INFO c.a.n.p.a.s.c.ClientAuthPluginManager - [ClientAuthPluginManager] Load ClientAuthService com.alibaba.nacos.client.auth.impl.NacosClientAuthServiceImpl success. 2025-07-01 13:37:23.615 [main] INFO c.a.n.p.a.s.c.ClientAuthPluginManager - [ClientAuthPluginManager] Load ClientAuthService com.alibaba.nacos.client.auth.ram.RamClientAuthServiceImpl success. 2025-07-01 13:37:23.625 [main] INFO c.a.n.c.a.r.i.CredentialWatcher - null No credential found 2025-07-01 13:37:24.817 [main] INFO o.a.coyote.http11.Http11NioProtocol - Starting ProtocolHandler ["http-nio-51801"] 2025-07-01 13:37:24.881 [main] INFO o.s.b.w.e.tomcat.TomcatWebServer - Tomcat started on port 51801 (http) with context path '/' 2025-07-01 13:37:24.910 [main] INFO com.alibaba.nacos.client.naming - initializer namespace from ans.namespace attribute : null 2025-07-01 13:37:24.911 [main] INFO com.alibaba.nacos.client.naming - initializer namespace from ALIBABA_ALIWARE_NAMESPACE attribute :null 2025-07-01 13:37:24.913 [main] INFO com.alibaba.nacos.client.naming - initializer namespace from namespace attribute :null 2025-07-01 13:37:25.022 [main] INFO c.a.n.p.a.s.c.ClientAuthPluginManager - [ClientAuthPluginManager] Load ClientAuthService com.alibaba.nacos.client.auth.impl.NacosClientAuthServiceImpl success. 2025-07-01 13:37:25.023 [main] INFO c.a.n.p.a.s.c.ClientAuthPluginManager - [ClientAuthPluginManager] Load ClientAuthService com.alibaba.nacos.client.auth.ram.RamClientAuthServiceImpl success. 2025-07-01 13:37:26.471 [main] INFO c.alibaba.nacos.common.remote.client - [RpcClientFactory] create a new rpc client of a52074fc-69d1-48b2-9aeb-d3875f5476f9 2025-07-01 13:37:26.694 [main] INFO c.alibaba.nacos.common.remote.client - [a52074fc-69d1-48b2-9aeb-d3875f5476f9] RpcClient init, ServerListFactory = com.alibaba.nacos.client.naming.core.ServerListManager 2025-07-01 13:37:26.695 [main] INFO c.alibaba.nacos.common.remote.client - [a52074fc-69d1-48b2-9aeb-d3875f5476f9] Registry connection listener to current client:com.alibaba.nacos.client.naming.remote.gprc.redo.NamingGrpcRedoService 2025-07-01 13:37:26.707 [main] INFO c.alibaba.nacos.common.remote.client - [a52074fc-69d1-48b2-9aeb-d3875f5476f9] Register server push request handler:com.alibaba.nacos.client.naming.remote.gprc.NamingPushRequestHandler 2025-07-01 13:37:26.720 [main] INFO c.alibaba.nacos.common.remote.client - [a52074fc-69d1-48b2-9aeb-d3875f5476f9] Try to connect to server on start up, server: {serverIp = '192.168.3.113', server main port = 8848} 2025-07-01 13:37:27.039 [main] INFO c.a.n.c.r.client.grpc.GrpcClient - grpc client connection server:192.168.3.113 ip,serverPort:9848,grpcTslConfig:{"sslProvider":"","enableTls":false,"mutualAuthEnable":false,"trustAll":false} 2025-07-01 13:37:29.706 [com.alibaba.nacos.client.naming.grpc.redo.0] WARN com.alibaba.nacos.client.naming - Grpc Connection is disconnect, skip current redo task 2025-07-01 13:37:30.973 [main] INFO c.alibaba.nacos.common.remote.client - [a52074fc-69d1-48b2-9aeb-d3875f5476f9] Success to connect to server [192.168.3.113:8848] on start up, connectionId = 1751348250562_192.168.3.113_5970 2025-07-01 13:37:30.974 [com.alibaba.nacos.client.remote.worker] INFO c.alibaba.nacos.common.remote.client - [a52074fc-69d1-48b2-9aeb-d3875f5476f9] Notify connected event to listeners. 2025-07-01 13:37:30.975 [com.alibaba.nacos.client.remote.worker] INFO com.alibaba.nacos.client.naming - Grpc connection connect 2025-07-01 13:37:30.975 [main] INFO c.alibaba.nacos.common.remote.client - [a52074fc-69d1-48b2-9aeb-d3875f5476f9] Register server push request handler:com.alibaba.nacos.common.remote.client.RpcClient$ConnectResetRequestHandler 2025-07-01 13:37:30.975 [main] INFO c.alibaba.nacos.common.remote.client - [a52074fc-69d1-48b2-9aeb-d3875f5476f9] Register server push request handler:com.alibaba.nacos.common.remote.client.RpcClient$$Lambda$1109/0x0000014db76cccf8 2025-07-01 13:37:30.977 [main] INFO com.alibaba.nacos.client.naming - [REGISTER-SERVICE] public registering service lingyidianke-leadnews-user with instance Instance{instanceId='null', ip='192.168.3.113', port=51801, weight=1.0, healthy=true, enabled=true, ephemeral=true, clusterName='', serviceName='null', metadata={IPv6=null, preserved.register.source=SPRING_CLOUD}} 2025-07-01 13:37:31.010 [main] INFO c.a.c.n.r.NacosServiceRegistry - nacos registry, DEFAULT_GROUP lingyidianke-leadnews-user 192.168.3.113:51801 register finished 2025-07-01 13:37:31.238 [main] INFO c.l.s.u.LingyidiankeLeadnewsUserApplication - Started LingyidiankeLeadnewsUserApplication in 18.411 seconds (process running for 21.381) 2025-07-01 13:37:31.241 [main] ERROR com.zaxxer.hikari.HikariConfig - HikariPool-1 - dataSource or dataSourceClassName or jdbcUrl is required. 2025-07-01 13:37:31.244 [main] INFO o.s.b.a.l.ConditionEvaluationReportLogger - Error starting ApplicationContext. To display the condition evaluation report re-run your application with 'debug' enabled. 2025-07-01 13:37:31.833 [main] INFO c.a.c.n.r.NacosServiceRegistry - De-registering from Nacos Server now... 2025-07-01 13:37:31.833 [main] INFO com.alibaba.nacos.client.naming - [DEREGISTER-SERVICE] public deregistering service lingyidianke-leadnews-user with instance: Instance{instanceId='null', ip='192.168.3.113', port=51801, weight=1.0, healthy=true, enabled=true, ephemeral=true, clusterName='', serviceName='null', metadata={}} 2025-07-01 13:37:31.852 [main] INFO c.a.c.n.r.NacosServiceRegistry - De-registration finished. 2025-07-01 13:37:31.853 [main] INFO com.alibaba.nacos.client.naming - com.alibaba.nacos.client.naming.cache.ServiceInfoHolder do shutdown begin 2025-07-01 13:37:31.853 [main] INFO com.alibaba.nacos.client.naming - com.alibaba.nacos.client.naming.backups.FailoverReactor do shutdown begin 2025-07-01 13:37:32.177 [main] INFO com.alibaba.nacos.client.naming - com.alibaba.nacos.client.naming.backups.FailoverReactor do shutdown stop 2025-07-01 13:37:32.177 [main] INFO com.alibaba.nacos.client.naming - com.alibaba.nacos.client.naming.cache.ServiceInfoHolder do shutdown stop 2025-07-01 13:37:32.177 [main] INFO com.alibaba.nacos.client.naming - com.alibaba.nacos.client.naming.remote.NamingClientProxyDelegate do shutdown begin 2025-07-01 13:37:32.179 [main] INFO com.alibaba.nacos.client.naming - com.alibaba.nacos.client.naming.core.ServiceInfoUpdateService do shutdown begin 2025-07-01 13:37:32.179 [main] INFO com.alibaba.nacos.client.naming - com.alibaba.nacos.client.naming.core.ServiceInfoUpdateService do shutdown stop 2025-07-01 13:37:32.179 [main] INFO com.alibaba.nacos.client.naming - com.alibaba.nacos.client.naming.core.ServerListManager do shutdown begin 2025-07-01 13:37:32.179 [main] WARN com.alibaba.nacos.client.naming - [NamingHttpClientManager] Start destroying NacosRestTemplate 2025-07-01 13:37:32.179 [main] WARN com.alibaba.nacos.client.naming - [NamingHttpClientManager] Destruction of the end 2025-07-01 13:37:32.179 [main] INFO com.alibaba.nacos.client.naming - com.alibaba.nacos.client.naming.core.ServerListManager do shutdown stop 2025-07-01 13:37:32.180 [main] INFO com.alibaba.nacos.client.naming - com.alibaba.nacos.client.naming.remote.http.NamingHttpClientProxy do shutdown begin 2025-07-01 13:37:32.180 [main] WARN com.alibaba.nacos.client.naming - [NamingHttpClientManager] Start destroying NacosRestTemplate 2025-07-01 13:37:32.180 [main] WARN com.alibaba.nacos.client.naming - [NamingHttpClientManager] Destruction of the end 2025-07-01 13:37:32.180 [main] INFO com.alibaba.nacos.client.naming - com.alibaba.nacos.client.naming.remote.http.NamingHttpClientProxy do shutdown stop 2025-07-01 13:37:32.180 [main] INFO c.alibaba.nacos.common.remote.client - Shutdown rpc client, set status to shutdown 2025-07-01 13:37:32.180 [main] INFO c.alibaba.nacos.common.remote.client - Shutdown client event executor java.util.concurrent.ScheduledThreadPoolExecutor@369a95a5[Running, pool size = 2, active threads = 2, queued tasks = 0, completed tasks = 0] 2025-07-01 13:37:32.181 [main] INFO c.alibaba.nacos.common.remote.client - Close current connection 1751348250562_192.168.3.113_5970 2025-07-01 13:37:32.187 [main] INFO c.a.n.c.r.client.grpc.GrpcClient - Shutdown grpc executor java.util.concurrent.ThreadPoolExecutor@2ac05a33[Running, pool size = 11, active threads = 0, queued tasks = 0, completed tasks = 11] 2025-07-01 13:37:32.188 [main] INFO com.alibaba.nacos.client.naming - Shutdown grpc redo service executor java.util.concurrent.ScheduledThreadPoolExecutor@35af52dc[Running, pool size = 1, active threads = 0, queued tasks = 1, completed tasks = 1] 2025-07-01 13:37:32.189 [main] INFO c.a.n.c.a.r.i.CredentialWatcher - [null] CredentialWatcher is stopped 2025-07-01 13:37:32.189 [main] INFO c.a.n.c.a.r.i.CredentialService - [null] CredentialService is freed 2025-07-01 13:37:32.189 [main] INFO com.alibaba.nacos.client.naming - com.alibaba.nacos.client.naming.remote.NamingClientProxyDelegate do shutdown stop 2025-07-01 13:37:32.272 [main] ERROR o.s.boot.SpringApplication - Application run failed java.lang.IllegalArgumentException: dataSource or dataSourceClassName or jdbcUrl is required. at com.zaxxer.hikari.HikariConfig.validate(HikariConfig.java:1032) at com.zaxxer.hikari.HikariDataSource.getConnection(HikariDataSource.java:108) at com.lingyidianke.service.user.LingyidiankeLeadnewsUserApplication.lambda$testDataSource$0(LingyidiankeLeadnewsUserApplication.java:60) at org.springframework.boot.SpringApplication.lambda$callRunner$5(SpringApplication.java:790) at org.springframework.util.function.ThrowingConsumer$1.acceptWithException(ThrowingConsumer.java:83) at org.springframework.util.function.ThrowingConsumer.accept(ThrowingConsumer.java:60) at org.springframework.util.function.ThrowingConsumer$1.accept(ThrowingConsumer.java:88) at org.springframework.boot.SpringApplication.callRunner(SpringApplication.java:798) at org.springframework.boot.SpringApplication.callRunner(SpringApplication.java:789) at org.springframework.boot.SpringApplication.lambda$callRunners$3(SpringApplication.java:774) at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:183) at java.base/java.util.stream.SortedOps$SizedRefSortingSink.end(SortedOps.java:357) at java.base/java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:510) at java.base/java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:499) at java.base/java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:150) at java.base/java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:173) at java.base/java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234) at java.base/java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:596) at org.springframework.boot.SpringApplication.callRunners(SpringApplication.java:774) at org.springframework.boot.SpringApplication.run(SpringApplication.java:342) at org.springframework.boot.SpringApplication.run(SpringApplication.java:1363) at org.springframework.boot.SpringApplication.run(SpringApplication.java:1352) at com.lingyidianke.service.user.LingyidiankeLeadnewsUserApplication.main(LingyidiankeLeadnewsUserApplication.java:32) 2025-07-01 13:37:32.277 [Thread-9] WARN c.a.nacos.common.notify.NotifyCenter - [NotifyCenter] Start destroying Publisher 2025-07-01 13:37:32.277 [Thread-3] WARN c.a.n.c.http.HttpClientBeanHolder - [HttpClientBeanHolder] Start destroying common HttpClient 2025-07-01 13:37:32.277 [Thread-9] WARN c.a.nacos.common.notify.NotifyCenter - [NotifyCenter] Destruction of the end 进程已结束,退出代码为 1 出问题了alArgumentException: dataSource or dataSourceClassName or jdbcUrl is required.,package com.lingyidianke.service.user; import com.baomidou.mybatisplus.annotation.DbType; import com.baomidou.mybatisplus.extension.plugins.MybatisPlusInterceptor; import com.baomidou.mybatisplus.extension.plugins.inner.PaginationInnerInterceptor; import com.zaxxer.hikari.HikariDataSource; import org.mybatis.spring.annotation.MapperScan; import org.slf4j.Logger; import org.slf4j.LoggerFactory; import org.springframework.beans.factory.annotation.Autowired; import org.springframework.boot.CommandLineRunner; import org.springframework.boot.SpringApplication; import org.springframework.boot.autoconfigure.SpringBootApplication; import org.springframework.cloud.client.discovery.EnableDiscoveryClient; import org.springframework.context.ConfigurableApplicationContext; import org.springframework.context.annotation.Bean; import org.springframework.context.annotation.Configuration; import org.springframework.core.env.Environment; import javax.sql.DataSource; import java.sql.Connection; import java.sql.SQLException; @SpringBootApplication @EnableDiscoveryClient @MapperScan("com.lingyidianke.service.user.mapper") public class LingyidiankeLeadnewsUserApplication { private static final Logger logger = LoggerFactory.getLogger(LingyidiankeLeadnewsUserApplication.class); public static void main(String[] args) { System.out.println("Application starting..."); ConfigurableApplicationContext context = SpringApplication.run(LingyidiankeLeadnewsUserApplication.class, args); // 验证日志系统是否正常工作 logger.info("Application started successfully."); checkEnvironment(context); validateMyBatisVersion(); } /** * 检查环境配置 */ private static void checkEnvironment(ConfigurableApplicationContext context) { Environment env = context.getEnvironment(); logger.info("Active profiles: {}", String.join(",", env.getActiveProfiles())); logger.info("Datasource URL: {}", env.getProperty("spring.datasource.url")); } /** * 验证数据源连接 */ @Autowired private DataSource dataSource; /** * 验证MyBatis运行时版本 */ @Bean public CommandLineRunner testDataSource(DataSource dataSource) { return args -> { try (Connection conn = dataSource.getConnection()) { logger.info("数据库连接成功: {}", conn.getMetaData().getURL()); } catch (SQLException e) { logger.error("数据库连接失败", e); } }; } private static void validateMyBatisVersion() { String version = Configuration.class.getPackage().getImplementationVersion(); logger.info("运行时MyBatis版本: {}", version); logger.error("当前版本:"); } }server: port: 51801 spring: application: name: lingyidianke-leadnews-user cloud: nacos: discovery: server-addr: 192.168.3.113:8848 username: nacos password: nacos config: server-addr: 192.168.3.113:8848 username: nacos password: nacos file-extension: yml extension-configs: # 与file-extension同级 - data-id: lingyidianke-leadnews-user-logging.yml group: DEFAULT_GROUP refresh: true # 启用动态刷新 main: allow-bean-definition-overriding: true # 开发环境允许Bean覆盖 # 日志配置(优先级低于Nacos配置) logging: config: classpath:logback-spring.xml file: path: D:/logs # 统一日志目录spring: application: name: lingyidianke-leadnews-user cloud: nacos: config: server-addr: 192.168.3.113:8848 namespace: public # 显式指定命名空间 data-id: ${spring.application.name}.yml # 动态引用应用名 group: DEFAULT_GROUP file-extension: yml refresh-enabled: true discovery: server-addr: ${spring.cloud.nacos.config.server-addr}
07-02
"C:\Program Files\Java\jdk-1.8\bin\java.exe" -Dpandora.location=E:\apache-maven-3.8.1-bin\taobao-hsf.sar-dev-SNAPSHOT.jar -Xmx1g -XX:TieredStopAtLevel=1 -noverify -Dspring.output.ansi.enabled=always -Dcom.sun.management.jmxremote -Dspring.jmx.enabled=true -Dspring.liveBeansView.mbeanDomain -Dspring.application.admin.enabled=true "-Dmanagement.endpoints.jmx.exposure.include=*" "-javaagent:E:\idea\IntelliJ IDEA 2023.2\lib\idea_rt.jar=53638:E:\idea\IntelliJ IDEA 2023.2\bin" -Dfile.encoding=UTF-8 -classpath C:\Users\Lplayer\AppData\Local\Temp\classpath1138593618.jar com.insigma.InsiisWebApplication fail to download http://mvnrepo.alibaba-inc.com/mvn/repository/com/alibaba/citrus/tool/antx-autoconfig/1.2-jdk9/antx-autoconfig-1.2-jdk9.jar to C:\Users\Lplayer\.autoconf\autoconf-1.2-jdk9.jar C:\Users\Lplayer\.autoconf\autoconf-1.2-jdk9.jar doesn't exist. ____ _ ____ _ | _ \ __ _ _ __ __| | ___ _ __ __ _ | __ ) ___ ___ | |_ | |_) / _` | '_ \ / _` |/ _ \| '__/ _` | | _ \ / _ \ / _ \| __| | __/ (_| | | | | (_| | (_) | | | (_| | | |_) | (_) | (_) | |_ |_| \__,_|_| |_|\__,_|\___/|_| \__,_| |____/ \___/ \___/ \__| :: Pandora Boot :: 2.1.9.1 Set log4j.defaultInitOverride to true. JM.Log:INFO Init JM logger with Log4jLoggerFactory JM.Log:INFO Log root path: C:\Users\Lplayer\logs\ JM.Log:INFO Set pandora log path: C:\Users\Lplayer\logs\pandora JM.Log:INFO Init JM logger with Log4jLoggerFactory JM.Log:INFO Log root path: C:\Users\Lplayer\logs\ JM.Log:INFO Set pandora log path: C:\Users\Lplayer\logs\pandora JM.Log:INFO Init JM logger with Log4jLoggerFactory JM.Log:INFO Log root path: C:\Users\Lplayer\logs\ JM.Log:INFO Set pandolet log path: C:\Users\Lplayer\logs\pandolet INFO: spas-client-initializer init Wed Aug 06 09:00:34 CST 2025 spas-sdk-client's ModuleClassLoader JM.Log:INFO Init JM logger with Slf4jLoggerFactory success, spas-sdk-client's ModuleClassLoader Wed Aug 06 09:00:34 CST 2025 spas-sdk-client's ModuleClassLoader JM.Log:INFO Log root path: C:\Users\Lplayer\logs\ Wed Aug 06 09:00:34 CST 2025 spas-sdk-client's ModuleClassLoader JM.Log:INFO Set spas log path: C:\Users\Lplayer\logs\spas Wed Aug 06 09:00:34 CST 2025 eagleeye-core's ModuleClassLoader JM.Log:INFO Init JM logger with Slf4jLoggerFactory success, eagleeye-core's ModuleClassLoader Wed Aug 06 09:00:34 CST 2025 eagleeye-core's ModuleClassLoader JM.Log:INFO Log root path: C:\Users\Lplayer\logs\ Wed Aug 06 09:00:34 CST 2025 eagleeye-core's ModuleClassLoader JM.Log:INFO Set metrics log path: C:\Users\Lplayer\logs\metrics Wed Aug 06 09:00:35 CST 2025 vipserver-client's ModuleClassLoader JM.Log:INFO Init JM logger with Log4jLoggerFactory, vipserver-client's ModuleClassLoader Wed Aug 06 09:00:35 CST 2025 vipserver-client's ModuleClassLoader JM.Log:INFO Log root path: C:\Users\Lplayer\logs\ Wed Aug 06 09:00:35 CST 2025 vipserver-client's ModuleClassLoader JM.Log:INFO Set vipsrv-logs log path: C:\Users\Lplayer\logs\vipsrv-logs Wed Aug 06 09:00:35 CST 2025 monitor's ModuleClassLoader JM.Log:INFO Init JM logger with Slf4jLoggerFactory success, monitor's ModuleClassLoader Wed Aug 06 09:00:35 CST 2025 monitor's ModuleClassLoader JM.Log:INFO Log root path: C:\Users\Lplayer\logs\ Wed Aug 06 09:00:35 CST 2025 monitor's ModuleClassLoader JM.Log:INFO Set tomcat-monitor log path: C:\Users\Lplayer\logs\tomcat-monitor Wed Aug 06 09:00:35 CST 2025 hsf's ModuleClassLoader JM.Log:INFO Init JM logger with Slf4jLoggerFactory success, hsf's ModuleClassLoader Wed Aug 06 09:00:35 CST 2025 hsf's ModuleClassLoader JM.Log:INFO Log root path: C:\Users\Lplayer\logs\ Wed Aug 06 09:00:35 CST 2025 hsf's ModuleClassLoader JM.Log:INFO Set hsf log path: C:\Users\Lplayer\logs\hsf SLF4J: Class path contains multiple SLF4J bindings. SLF4J: Found binding in [jar:file:/E:/apache-maven-3.8.1-bin/taobao-hsf.sar-dev-SNAPSHOT.jar!/plugins/hsf!/lib/logback-classic-1.2.3.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: Found binding in [jar:file:/E:/apache-maven-3.8.1-bin/taobao-hsf.sar-dev-SNAPSHOT.jar!/plugins/hsf!/lib/slf4j-log4j12-1.6.1.jar!/org/slf4j/impl/StaticLoggerBinder.class] SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder] *******************HSF PORT:12200 ************** *************Pandora QOS PORT:12201 ************** *************Tomcat Monitor Port:8006 ************** *******************Sentinel PORT:8719 ************** log4j:WARN No appenders could be found for logger (io.netty.util.internal.logging.InternalLoggerFactory). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. **************************************************************************************** ** ** ** Pandora Container ** ** ** ** Pandora Host: 10.66.242.118 ** ** Pandora Version: 2.1.4 ** ** SAR Version: edas.sar.V3.5.3 ** ** Package Time: 2025-08-06 09:00:32 ** ** ** ** Plug-in Modules: 19 ** ** ** ** metrics .......................................... 1.7.0 ** ** edas-assist ...................................... 2.0 ** ** pandora-qos-service .............................. edas215 ** ** pandolet ......................................... 1.0.0 ** ** spas-sdk-client .................................. 1.3.0 ** ** eagleeye-core .................................... 1.7.10.1 ** ** tddl-driver ...................................... 1.0.5-SNAPSHOT ** ** vipserver-client ................................. 4.7.9-SNAPSHOT ** ** diamond-client ................................... 3.8.10 ** ** configcenter-client .............................. 1.0.3 ** ** spas-sdk-service ................................. 1.3.0 ** ** dpath ............................................ 1.4 ** ** config-client .................................... 1.9.6 ** ** unitrouter ....................................... 1.0.11 ** ** monitor .......................................... 1.2.3-SNAPSHOT ** ** sentinel-plugin .................................. 2.12.12-edas ** ** ons-client ....................................... 1.8.0-EagleEye ** ** hsf .............................................. 2.2.7.3.1-TLS ** ** pandora-framework ................................ 2.0.8 ** ** ** ** [WARNING] All these plug-in modules will override maven pom.xml dependencies. ** ** More: http://gitlab.alibaba-inc.com/middleware-container/pandora/wikis/home ** ** ** **************************************************************************************** INFO: spas-client-initializer start JM.Log:INFO Init JM logger with Log4jLoggerFactory JM.Log:INFO Log root path: C:\Users\Lplayer\logs\ JM.Log:INFO Set pandora log path: C:\Users\Lplayer\logs\pandora Init available components Scanning for available components in the runtime Starting available components Skip ProjectInfoInitializer. 2025-08-06 09:00:37.814 INFO 3324 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration' of type [org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration$$EnhancerBySpringCGLIB$$dd14cfb2] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2025-08-06 09:00:37.845 INFO 3324 --- [ main] c.a.c.c.acm.AliCloudAcmInitializer : Initialize acm from acm configuration. . ____ _ __ _ _ /\\ / ___'_ __ _ _(_)_ __ __ _ \ \ \ \ ( ( )\___ | '_ | '_| | '_ \/ _` | \ \ \ \ \\/ ___)| |_)| | | | | || (_| | ) ) ) ) ' |____| .__|_| |_|_| |_\__, | / / / / =========|_|==============|___/=/_/_/_/ :: Spring Boot :: (v2.1.4.RELEASE) Wed Aug 06 09:00:38 CST 2025 diamond-client's ModuleClassLoader JM.Log:INFO Init JM logger with Slf4jLoggerFactory success, diamond-client's ModuleClassLoader Wed Aug 06 09:00:38 CST 2025 diamond-client's ModuleClassLoader JM.Log:INFO Log root path: C:\Users\Lplayer\logs\ Wed Aug 06 09:00:38 CST 2025 diamond-client's ModuleClassLoader JM.Log:INFO Set diamond-client log path: C:\Users\Lplayer\logs\diamond-client 09:00:38.851 [main] INFO c.t.d.identify.CredentialWatcher - [] [] [] No credential found 2025-08-06 09:00:38.961 INFO 3324 --- [ main] b.c.PropertySourceBootstrapConfiguration : Located property source: CompositePropertySource {name='diamond', propertySources=[]} Skip ProjectInfoInitializer. 2025-08-06 09:00:38.981 INFO 3324 --- [ main] com.insigma.InsiisWebApplication : The following profiles are active: redis,datasource,security,mybatis,async 2025-08-06 09:00:42.299 INFO 3324 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Multiple Spring Data modules found, entering strict repository configuration mode! 2025-08-06 09:00:42.299 INFO 3324 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data repositories in DEFAULT mode. 2025-08-06 09:00:42.810 INFO 3324 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 503ms. Found 21 repository interfaces. 2025-08-06 09:00:42.817 INFO 3324 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Multiple Spring Data modules found, entering strict repository configuration mode! 2025-08-06 09:00:42.817 INFO 3324 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data repositories in DEFAULT mode. 2025-08-06 09:00:42.981 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data MongoDB - Could not safely identify store assignment for repository candidate interface com.insigma.sys.repository.Aa26Repository. 2025-08-06 09:00:42.982 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data MongoDB - Could not safely identify store assignment for repository candidate interface com.insigma.sys.repository.MenuRepository. 2025-08-06 09:00:42.982 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data MongoDB - Could not safely identify store assignment for repository candidate interface com.insigma.sys.repository.RoleRepository. 2025-08-06 09:00:42.983 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data MongoDB - Could not safely identify store assignment for repository candidate interface com.insigma.sys.repository.SysCodeRepository. 2025-08-06 09:00:42.983 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data MongoDB - Could not safely identify store assignment for repository candidate interface com.insigma.sys.repository.SysErrorRepository. 2025-08-06 09:00:42.983 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data MongoDB - Could not safely identify store assignment for repository candidate interface com.insigma.sys.repository.SysHolidayRepository. 2025-08-06 09:00:42.983 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data MongoDB - Could not safely identify store assignment for repository candidate interface com.insigma.sys.repository.SysIdMappingRespository. 2025-08-06 09:00:42.984 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data MongoDB - Could not safely identify store assignment for repository candidate interface com.insigma.sys.repository.SysOrgRepository. 2025-08-06 09:00:42.984 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data MongoDB - Could not safely identify store assignment for repository candidate interface com.insigma.sys.repository.SysRoleFunctionRepository. 2025-08-06 09:00:42.984 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data MongoDB - Could not safely identify store assignment for repository candidate interface com.insigma.sys.repository.SysUserAreaRepository. 2025-08-06 09:00:42.985 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data MongoDB - Could not safely identify store assignment for repository candidate interface com.insigma.sys.repository.SysUserRepository. 2025-08-06 09:00:42.986 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data MongoDB - Could not safely identify store assignment for repository candidate interface com.insigma.sys.repository.SysUserRoleRepository. 2025-08-06 09:00:42.986 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data MongoDB - Could not safely identify store assignment for repository candidate interface com.insigma.drugs.repository.ProtalDrugsRepository. 2025-08-06 09:00:42.986 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data MongoDB - Could not safely identify store assignment for repository candidate interface com.insigma.framework.oplog.repository.OpLogRepository. 2025-08-06 09:00:42.986 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data MongoDB - Could not safely identify store assignment for repository candidate interface com.insigma.framework.commons.repository.SysOperateLogRepository. 2025-08-06 09:00:42.987 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data MongoDB - Could not safely identify store assignment for repository candidate interface com.insigma.framework.oplog.repository.OpLogFormRepository. 2025-08-06 09:00:42.987 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data MongoDB - Could not safely identify store assignment for repository candidate interface com.insigma.web.support.dao.Aa01Repository. 2025-08-06 09:00:42.989 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data MongoDB - Could not safely identify store assignment for repository candidate interface com.insigma.web.support.dao.CodeTypeRepository. 2025-08-06 09:00:42.989 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data MongoDB - Could not safely identify store assignment for repository candidate interface com.insigma.web.support.dao.MdParamRepository. 2025-08-06 09:00:42.989 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data MongoDB - Could not safely identify store assignment for repository candidate interface com.insigma.framework.web.securities.repository.SysLogonLogRepository. 2025-08-06 09:00:43.026 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data MongoDB - Could not safely identify store assignment for repository candidate interface com.insigma.framework.web.securities.repository.SysLogonLogRepository. 2025-08-06 09:00:43.027 INFO 3324 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 210ms. Found 0 repository interfaces. 2025-08-06 09:00:43.038 INFO 3324 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Multiple Spring Data modules found, entering strict repository configuration mode! 2025-08-06 09:00:43.039 INFO 3324 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data repositories in DEFAULT mode. 2025-08-06 09:00:43.205 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data Redis - Could not safely identify store assignment for repository candidate interface com.insigma.sys.repository.Aa26Repository. 2025-08-06 09:00:43.205 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data Redis - Could not safely identify store assignment for repository candidate interface com.insigma.sys.repository.MenuRepository. 2025-08-06 09:00:43.205 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data Redis - Could not safely identify store assignment for repository candidate interface com.insigma.sys.repository.RoleRepository. 2025-08-06 09:00:43.205 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data Redis - Could not safely identify store assignment for repository candidate interface com.insigma.sys.repository.SysCodeRepository. 2025-08-06 09:00:43.206 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data Redis - Could not safely identify store assignment for repository candidate interface com.insigma.sys.repository.SysErrorRepository. 2025-08-06 09:00:43.206 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data Redis - Could not safely identify store assignment for repository candidate interface com.insigma.sys.repository.SysHolidayRepository. 2025-08-06 09:00:43.206 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data Redis - Could not safely identify store assignment for repository candidate interface com.insigma.sys.repository.SysIdMappingRespository. 2025-08-06 09:00:43.206 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data Redis - Could not safely identify store assignment for repository candidate interface com.insigma.sys.repository.SysOrgRepository. 2025-08-06 09:00:43.206 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data Redis - Could not safely identify store assignment for repository candidate interface com.insigma.sys.repository.SysRoleFunctionRepository. 2025-08-06 09:00:43.206 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data Redis - Could not safely identify store assignment for repository candidate interface com.insigma.sys.repository.SysUserAreaRepository. 2025-08-06 09:00:43.206 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data Redis - Could not safely identify store assignment for repository candidate interface com.insigma.sys.repository.SysUserRepository. 2025-08-06 09:00:43.207 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data Redis - Could not safely identify store assignment for repository candidate interface com.insigma.sys.repository.SysUserRoleRepository. 2025-08-06 09:00:43.207 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data Redis - Could not safely identify store assignment for repository candidate interface com.insigma.drugs.repository.ProtalDrugsRepository. 2025-08-06 09:00:43.207 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data Redis - Could not safely identify store assignment for repository candidate interface com.insigma.framework.oplog.repository.OpLogRepository. 2025-08-06 09:00:43.207 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data Redis - Could not safely identify store assignment for repository candidate interface com.insigma.framework.commons.repository.SysOperateLogRepository. 2025-08-06 09:00:43.207 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data Redis - Could not safely identify store assignment for repository candidate interface com.insigma.framework.oplog.repository.OpLogFormRepository. 2025-08-06 09:00:43.207 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data Redis - Could not safely identify store assignment for repository candidate interface com.insigma.web.support.dao.Aa01Repository. 2025-08-06 09:00:43.207 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data Redis - Could not safely identify store assignment for repository candidate interface com.insigma.web.support.dao.CodeTypeRepository. 2025-08-06 09:00:43.207 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data Redis - Could not safely identify store assignment for repository candidate interface com.insigma.web.support.dao.MdParamRepository. 2025-08-06 09:00:43.207 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data Redis - Could not safely identify store assignment for repository candidate interface com.insigma.framework.web.securities.repository.SysLogonLogRepository. 2025-08-06 09:00:43.231 INFO 3324 --- [ main] .RepositoryConfigurationExtensionSupport : Spring Data Redis - Could not safely identify store assignment for repository candidate interface com.insigma.framework.web.securities.repository.SysLogonLogRepository. 2025-08-06 09:00:43.231 INFO 3324 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 184ms. Found 0 repository interfaces. 2025-08-06 09:00:43.414 WARN 3324 --- [ main] o.m.s.mapper.ClassPathMapperScanner : Skipping MapperFactoryBean with name 'caseInfoDDao' and 'com.insigma.business.bigdata.dao.CaseInfoDDao' mapperInterface. Bean already defined with the same name! 2025-08-06 09:00:43.515 INFO 3324 --- [ main] o.s.cloud.context.scope.GenericScope : BeanFactory id=715b0589-9638-3765-9a2d-50e339059fc9 2025-08-06 09:00:43.637 INFO 3324 --- [ main] c.a.b.h.c.HsfConsumerPostProcessor : registered HSFConsumerBean "queryAdmdvsService" in spring context. 2025-08-06 09:00:43.637 INFO 3324 --- [ main] c.a.b.h.c.HsfConsumerPostProcessor : registered HSFConsumerBean "queryDataDicService" in spring context. 2025-08-06 09:00:43.637 INFO 3324 --- [ main] c.a.b.h.c.HsfConsumerPostProcessor : registered HSFConsumerBean "roleAuthInfoService" in spring context. 2025-08-06 09:00:43.637 INFO 3324 --- [ main] c.a.b.h.c.HsfConsumerPostProcessor : registered HSFConsumerBean "admrolService" in spring context. 2025-08-06 09:00:43.637 INFO 3324 --- [ main] c.a.b.h.c.HsfConsumerPostProcessor : registered HSFConsumerBean "orguntService" in spring context. 2025-08-06 09:00:43.637 INFO 3324 --- [ main] c.a.b.h.c.HsfConsumerPostProcessor : registered HSFConsumerBean "unitService" in spring context. 2025-08-06 09:00:43.637 INFO 3324 --- [ main] c.a.b.h.c.HsfConsumerPostProcessor : registered HSFConsumerBean "userService" in spring context. 2025-08-06 09:00:43.637 INFO 3324 --- [ main] c.a.b.h.c.HsfConsumerPostProcessor : registered HSFConsumerBean "sysUactService" in spring context. 2025-08-06 09:00:43.637 INFO 3324 --- [ main] c.a.b.h.c.HsfConsumerPostProcessor : registered HSFConsumerBean "resuService" in spring context. 2025-08-06 09:00:43.637 INFO 3324 --- [ main] c.a.b.h.c.HsfConsumerPostProcessor : registered HSFConsumerBean "bizrolService" in spring context. 2025-08-06 09:00:43.637 INFO 3324 --- [ main] c.a.b.h.c.HsfConsumerPostProcessor : registered HSFConsumerBean "publicFeedetlChkDetMgtService" in spring context. Wed Aug 06 09:00:43 CST 2025 dpath's ModuleClassLoader JM.Log:INFO Init JM logger with Slf4jLoggerFactory success, dpath's ModuleClassLoader Wed Aug 06 09:00:43 CST 2025 dpath's ModuleClassLoader JM.Log:INFO Log root path: C:\Users\Lplayer\logs\ Wed Aug 06 09:00:43 CST 2025 dpath's ModuleClassLoader JM.Log:INFO Set dpath log path: C:\Users\Lplayer\logs\dpath Wed Aug 06 09:00:43 CST 2025 dpath's ModuleClassLoader JM.Log:INFO Can't find method for class ch.qos.logback.classic.AsyncAppender setMaxFlushTime 3000 Wed Aug 06 09:00:43 CST 2025 dpath's ModuleClassLoader JM.Log:INFO Can't find method for class ch.qos.logback.classic.AsyncAppender setNeverBlock true Wed Aug 06 09:00:46 CST 2025 config-client's ModuleClassLoader JM.Log:INFO Init JM logger with Slf4jLoggerFactory success, config-client's ModuleClassLoader Wed Aug 06 09:00:46 CST 2025 config-client's ModuleClassLoader JM.Log:INFO Log root path: C:\Users\Lplayer\logs\ 09:00:46.888 [HSF-Framework-ExportRefer-14-thread-1] INFO ConfigClientLogger - [] [] [] JM_CC_LOG_RETAIN_COUNT:6, JM_LOG_FILE_SIZE:200MB Wed Aug 06 09:00:46 CST 2025 config-client's ModuleClassLoader JM.Log:INFO Set configclient log path: C:\Users\Lplayer\logs\configclient 2025-08-06 09:00:49.973 INFO 3324 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'queryAdmdvsService' of type [com.taobao.hsf.app.spring.util.HSFSpringConsumerBean] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2025-08-06 09:00:52.994 INFO 3324 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'queryDataDicService' of type [com.taobao.hsf.app.spring.util.HSFSpringConsumerBean] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2025-08-06 09:00:56.018 INFO 3324 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'roleAuthInfoService' of type [com.taobao.hsf.app.spring.util.HSFSpringConsumerBean] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2025-08-06 09:00:59.040 INFO 3324 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'admrolService' of type [com.taobao.hsf.app.spring.util.HSFSpringConsumerBean] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2025-08-06 09:01:02.062 INFO 3324 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'orguntService' of type [com.taobao.hsf.app.spring.util.HSFSpringConsumerBean] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2025-08-06 09:01:05.082 INFO 3324 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'unitService' of type [com.taobao.hsf.app.spring.util.HSFSpringConsumerBean] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2025-08-06 09:01:08.103 INFO 3324 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'userService' of type [com.taobao.hsf.app.spring.util.HSFSpringConsumerBean] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2025-08-06 09:01:11.121 INFO 3324 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'sysUactService' of type [com.taobao.hsf.app.spring.util.HSFSpringConsumerBean] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2025-08-06 09:01:14.146 INFO 3324 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'resuService' of type [com.taobao.hsf.app.spring.util.HSFSpringConsumerBean] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2025-08-06 09:01:17.170 INFO 3324 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'bizrolService' of type [com.taobao.hsf.app.spring.util.HSFSpringConsumerBean] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2025-08-06 09:01:20.193 INFO 3324 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'publicFeedetlChkDetMgtService' of type [com.taobao.hsf.app.spring.util.HSFSpringConsumerBean] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2025-08-06 09:01:20.270 INFO 3324 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration' of type [org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration$$EnhancerBySpringCGLIB$$c0faccb5] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2025-08-06 09:01:20.378 INFO 3324 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'redisConfig' of type [com.insigma.web.support.redis.RedisConfig$$EnhancerBySpringCGLIB$$20be0ef0] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2025-08-06 09:01:20.401 INFO 3324 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'multipleDataSourceConfig' of type [com.insigma.hsaf.common.config.MultipleDataSourceConfig$$EnhancerBySpringCGLIB$$1e06f17d] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2025-08-06 09:01:20.432 INFO 3324 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'spring.datasource-org.springframework.boot.autoconfigure.jdbc.DataSourceProperties' of type [org.springframework.boot.autoconfigure.jdbc.DataSourceProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2025-08-06 09:01:20.475 INFO 3324 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'com.alibaba.druid.spring.boot.autoconfigure.stat.DruidFilterConfiguration' of type [com.alibaba.druid.spring.boot.autoconfigure.stat.DruidFilterConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2025-08-06 09:01:20.492 INFO 3324 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'statFilter' of type [com.alibaba.druid.filter.stat.StatFilter] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2025-08-06 09:01:20.597 INFO 3324 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'wallConfig' of type [com.alibaba.druid.wall.WallConfig] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2025-08-06 09:01:20.616 INFO 3324 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'wallFilter' of type [com.alibaba.druid.wall.WallFilter] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2025-08-06 09:01:20.676 INFO 3324 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'slf4jLogFilter' of type [com.alibaba.druid.filter.logging.Slf4jLogFilter] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) Wed Aug 06 09:01:20 CST 2025 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. Wed Aug 06 09:01:20 CST 2025 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. Wed Aug 06 09:01:20 CST 2025 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. Wed Aug 06 09:01:20 CST 2025 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. Wed Aug 06 09:01:21 CST 2025 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. 2025-08-06 09:01:21.030 INFO 3324 --- [ main] com.alibaba.druid.pool.DruidDataSource : {dataSource-1} inited 2025-08-06 09:01:21.030 INFO 3324 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'primaryDataSource' of type [com.insigma.hsaf.common.config.MultipleDataSourceConfig$DruidDataSourceWrapper] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2025-08-06 09:01:21.074 INFO 3324 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.jdbc.DataSourceInitializerInvoker' of type [org.springframework.boot.autoconfigure.jdbc.DataSourceInitializerInvoker] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2025-08-06 09:01:21.086 INFO 3324 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'spring.jdbc-org.springframework.boot.autoconfigure.jdbc.JdbcProperties' of type [org.springframework.boot.autoconfigure.jdbc.JdbcProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2025-08-06 09:01:21.087 INFO 3324 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.jdbc.JdbcTemplateAutoConfiguration$JdbcTemplateConfiguration' of type [org.springframework.boot.autoconfigure.jdbc.JdbcTemplateAutoConfiguration$JdbcTemplateConfiguration$$EnhancerBySpringCGLIB$$d985fb22] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2025-08-06 09:01:21.097 INFO 3324 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'jdbcTemplate' of type [org.springframework.jdbc.core.JdbcTemplate] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2025-08-06 09:01:21.117 INFO 3324 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'odinLogServiceImpl' of type [com.insigma.framework.log.service.impl.OdinLogServiceImpl] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2025-08-06 09:01:21.136 INFO 3324 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'odinLogAspect' of type [com.insigma.framework.log.OdinLogAspect] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2025-08-06 09:01:21.144 INFO 3324 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration' of type [org.springframework.cloud.autoconfigure.ConfigurationPropertiesRebinderAutoConfiguration$$EnhancerBySpringCGLIB$$dd14cfb2] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying) 2025-08-06 09:01:21.458 INFO 3324 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port(s): 9100 (http) 八月 06, 2025 9:01:21 上午 org.apache.coyote.AbstractProtocol init 信息: Initializing ProtocolHandler ["http-nio-9100"] log4j:WARN No appenders could be found for logger (org.apache.coyote.http11.Http11NioProtocol). log4j:WARN Please initialize the log4j system properly. log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info. 八月 06, 2025 9:01:21 上午 org.apache.catalina.core.StandardService startInternal 信息: Starting service [Tomcat] 八月 06, 2025 9:01:21 上午 org.apache.catalina.core.StandardEngine startInternal 信息: Starting Servlet engine: [Apache Tomcat/9.0.17] 八月 06, 2025 9:01:21 上午 org.apache.catalina.core.AprLifecycleListener lifecycleEvent 信息: Loaded APR based Apache Tomcat Native library [1.3.1] using APR version [1.7.4]. 八月 06, 2025 9:01:21 上午 org.apache.catalina.core.AprLifecycleListener lifecycleEvent 信息: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true]. 八月 06, 2025 9:01:21 上午 org.apache.catalina.core.AprLifecycleListener lifecycleEvent 信息: APR/OpenSSL configuration: useAprConnector [false], useOpenSSL [true] 八月 06, 2025 9:01:21 上午 org.apache.catalina.core.AprLifecycleListener initializeSSL 信息: OpenSSL successfully initialized [OpenSSL 3.0.14 4 Jun 2024] 八月 06, 2025 9:01:21 上午 org.apache.catalina.core.ApplicationContext log 信息: Initializing Spring embedded WebApplicationContext 2025-08-06 09:01:21.555 INFO 3324 --- [ main] o.s.web.context.ContextLoader : Root WebApplicationContext: initialization completed in 42560 ms 2025-08-06 09:01:21.567 INFO 3324 --- [ main] c.i.f.system.safety.SysSafetyProperties : sql: SysSafetyProperties.SQL(badstr=null) System is starting! UTF-8:一个汉字的字节数为:3 2025-08-06 09:01:22.651 INFO 3324 --- [ main] c.i.o.f.safe.validate.SignatureValidate : li: anytomcat2023-03-04anyunlimitedinsiisunlimited安徽省医保核心配置文件anyWindowsTf-c4-d3-UZ-d3-1646357567308502[][]10安徽省医保(核三框架)DEVELOP[{}]rule=0, version=6.0delay=0, extend=, format=2, product=insiis, release=1.0 2025-08-06 09:01:22.652 INFO 3324 --- [ main] c.i.o.f.safe.validate.SignatureValidate : 9180cd3c218c8736c1a23333546bff22f4017978 2025-08-06 09:01:22.666 INFO 3324 --- [ main] c.i.o.f.safe.ValidateContExecute : Apache Tomcat/9.0.17 您的核心配置文件已经失效测!请及时更换。Your core config have expired! Please update it! 2025-08-06 09:01:23.038 INFO 3324 --- [ main] c.i.o.f.safe.ValidateContExecute : IP: [127.0.0.1, 0:0:0:0:0:0:0:1, fe80:0:0:0:cb88:c7b3:57ec:13b3%eth3, fe80:0:0:0:6d46:2122:72d0:9648%eth4, 10.66.242.118, fe80:0:0:0:b0b9:6640:37a:c4b2%eth5, fe80:0:0:0:83dc:74e7:38e:235b%eth7, fe80:0:0:0:fc5c:c0e0:f227:7889%wlan0, 192.168.18.1, fe80:0:0:0:b714:55b0:2962:c0f2%eth9, 192.168.163.1, fe80:0:0:0:d554:a3f0:a6ea:47d3%eth10, fe80:0:0:0:aed2:bc06:dc31:db57%wlan1, 192.168.83.243, 240e:45a:48d:67c2:6dbd:62cf:5eda:307c, 240e:45a:48d:67c2:fddf:2d50:d7db:573f, fe80:0:0:0:2dc6:6f4:b194:de03%wlan2] 2025-08-06 09:01:23.038 INFO 3324 --- [ main] c.i.o.f.safe.ValidateContExecute : CPU core: 20 2025-08-06 09:01:23.039 INFO 3324 --- [ main] c.i.o.f.safe.ValidateContExecute : Windows 11 10.0 2025-08-06 09:01:23.100 INFO 3324 --- [ main] c.i.o.f.safe.ValidateContExecute : Computer MAC: [] 2025-08-06 09:01:23.409 INFO 3324 --- [ main] o.hibernate.jpa.internal.util.LogHelper : HHH000204: Processing PersistenceUnitInfo [ name: default ...] 2025-08-06 09:01:23.476 INFO 3324 --- [ main] org.hibernate.Version : HHH000412: Hibernate Core {5.0.12.Final} 2025-08-06 09:01:23.478 INFO 3324 --- [ main] org.hibernate.cfg.Environment : HHH000206: hibernate.properties not found 2025-08-06 09:01:23.479 INFO 3324 --- [ main] org.hibernate.cfg.Environment : HHH000021: Bytecode provider name : javassist 2025-08-06 09:01:23.522 INFO 3324 --- [ main] o.hibernate.annotations.common.Version : HCANN000001: Hibernate Commons Annotations {5.0.1.Final} 2025-08-06 09:01:23.613 INFO 3324 --- [ main] org.hibernate.dialect.Dialect : HHH000400: Using dialect: org.hibernate.dialect.MySQL5InnoDBDialect 2025-08-06 09:01:23.775 WARN 3324 --- [ main] org.hibernate.id.UUIDHexGenerator : HHH000409: Using org.hibernate.id.UUIDHexGenerator which does not generate IETF RFC 4122 compliant UUID values; consider using org.hibernate.id.UUIDGenerator instead 2025-08-06 09:01:24.127 INFO 3324 --- [ main] j.LocalContainerEntityManagerFactoryBean : Initialized JPA EntityManagerFactory for persistence unit 'default' 2025-08-06 09:01:25.142 INFO 3324 --- [ main] io.lettuce.core.EpollProvider : Starting without optional epoll library 2025-08-06 09:01:25.143 INFO 3324 --- [ main] io.lettuce.core.KqueueProvider : Starting without optional kqueue library 2025-08-06 09:01:26.137 INFO 3324 --- [ main] c.i.h.c.a.cache.AdmdvsDimCacheManager : init admdvsDim Start 2025-08-06 09:01:27.066 INFO 3324 --- [ main] c.i.h.c.a.cache.AdmdvsDimCacheManager : init admdvsDim End 2025-08-06 09:01:27.635 INFO 3324 --- [ main] o.h.h.i.QueryTranslatorFactoryInitiator : HHH000397: Using ASTQueryTranslatorFactory 2025-08-06 09:01:27.993 INFO 3324 --- [ main] com.alibaba.druid.pool.DruidDataSource : {dataSource-2} inited 2025-08-06 09:01:28.092 INFO 3324 --- [ main] f.a.AutowiredAnnotationBeanPostProcessor : Autowired annotation is not supported on static fields: private static boolean com.insigma.sys.common.SysManageMode.tripleMode 2025-08-06 09:01:28.136 INFO 3324 --- [ main] com.insigma.sys.config.UEditorConfig : 读取UEditor配置文件成功! 2025-08-06 09:01:28.808 INFO 3324 --- [ main] c.i.hsa.common.base.job.CacheRefreshJob : begin refresh enforce dict cache ... 2025-08-06 09:01:28.809 INFO 3324 --- [ main] c.i.hsa.common.base.job.CacheRefreshJob : success refresh enforce dict cache ... 2025-08-06 09:01:28.809 INFO 3324 --- [ main] c.i.hsa.common.base.job.CacheRefreshJob : begin refresh enforce admdvsDim cache ... 2025-08-06 09:01:28.815 INFO 3324 --- [ main] c.i.h.c.a.cache.AdmdvsDimCacheManager : init admdvsDim Start 2025-08-06 09:01:29.615 INFO 3324 --- [ main] c.i.h.c.a.cache.AdmdvsDimCacheManager : init admdvsDim End 2025-08-06 09:01:29.615 INFO 3324 --- [ main] c.i.hsa.common.base.job.CacheRefreshJob : success refresh enforce admdvsDim cache ... 2025-08-06 09:01:29.627 INFO 3324 --- [ main] f.a.AutowiredAnnotationBeanPostProcessor : Autowired annotation is not supported on static methods: public static void com.insigma.hsa.common.excel.ExcelUtils.setPageSize(int) 2025-08-06 09:01:29.735 WARN 3324 --- [ main] c.i.framework.GlobalExceptionCollector : 没有找到公共服务异常统一管理方法[call4Exception],该功能将自动关闭! 2025-08-06 09:01:30.454 INFO 3324 --- [ main] o.s.s.concurrent.ThreadPoolTaskExecutor : Initializing ExecutorService 'applicationTaskExecutor' 2025-08-06 09:01:30.519 WARN 3324 --- [ main] aWebConfiguration$JpaWebMvcConfiguration : 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 Logging initialized using 'class org.apache.ibatis.logging.stdout.StdOutImpl' adapter. 2025-08-06 09:01:31.239 INFO 3324 --- [ main] .s.s.UserDetailsServiceAutoConfiguration : Using generated security password: f0640dd2-67b8-4024-bdd5-51708f0024e3 2025-08-06 09:01:31.321 INFO 3324 --- [ main] o.s.s.web.DefaultSecurityFilterChain : Creating filter chain: org.springframework.security.web.util.matcher.AnyRequestMatcher@1, [org.springframework.security.web.context.request.async.WebAsyncManagerIntegrationFilter@34fd82cd, org.springframework.security.web.context.SecurityContextPersistenceFilter@18010665, org.springframework.security.web.header.HeaderWriterFilter@2e41e742, org.springframework.security.web.authentication.logout.LogoutFilter@203b2f14, com.insigma.hsaf.security.web.support.SSOUserContextFilter@28d38918, org.springframework.security.web.savedrequest.RequestCacheAwareFilter@19f1d1d, org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter@2a5b5e33, org.springframework.security.web.authentication.AnonymousAuthenticationFilter@14029881, org.springframework.security.web.session.SessionManagementFilter@307d7688, org.springframework.security.web.access.ExceptionTranslationFilter@5e09b1a6, org.springframework.security.web.access.intercept.FilterSecurityInterceptor@ddbbb82] 2025-08-06 09:01:31.325 INFO 3324 --- [ main] o.s.s.web.DefaultSecurityFilterChain : Creating filter chain: org.springframework.security.web.util.matcher.AnyRequestMatcher@1, [org.springframework.security.web.context.request.async.WebAsyncManagerIntegrationFilter@1925b878, org.springframework.security.web.context.SecurityContextPersistenceFilter@e449c7c, org.springframework.security.web.header.HeaderWriterFilter@4464aae2, org.springframework.security.web.authentication.logout.LogoutFilter@247dd07, org.springframework.security.web.savedrequest.RequestCacheAwareFilter@112d42ba, org.springframework.security.web.servletapi.SecurityContextHolderAwareRequestFilter@707fc9c7, org.springframework.security.web.authentication.AnonymousAuthenticationFilter@7f9b0fb, org.springframework.security.web.session.SessionManagementFilter@238a281f, org.springframework.security.web.access.ExceptionTranslationFilter@63ff8137, org.springframework.security.web.access.intercept.FilterSecurityInterceptor@61a5226d] 2025-08-06 09:01:32.445 INFO 3324 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port(s): 7099 (http) 2025-08-06 09:01:32.451 INFO 3324 --- [ main] o.s.web.context.ContextLoader : Root WebApplicationContext: initialization completed in 81 ms 八月 06, 2025 9:01:32 上午 org.apache.coyote.AbstractProtocol init 信息: Initializing ProtocolHandler ["http-nio-7099"] 八月 06, 2025 9:01:32 上午 org.apache.catalina.core.StandardService startInternal 信息: Starting service [Tomcat] 八月 06, 2025 9:01:32 上午 org.apache.catalina.core.StandardEngine startInternal 信息: Starting Servlet engine: [Apache Tomcat/9.0.17] 八月 06, 2025 9:01:32 上午 org.apache.catalina.core.ApplicationContext log 信息: Initializing Spring embedded WebApplicationContext 2025-08-06 09:01:32.465 INFO 3324 --- [ main] o.s.b.a.e.web.EndpointLinksResolver : Exposing 2 endpoint(s) beneath base path '/actuator' 2025-08-06 09:01:32.501 INFO 3324 --- [ool-20-thread-1] c.i.h.c.d.impl.DataDicLocalServiceImpl : DataDicLocalServiceImpl---------getDataDict--------start 八月 06, 2025 9:01:32 上午 org.apache.coyote.AbstractProtocol start 信息: Starting ProtocolHandler ["http-nio-7099"] 2025-08-06 09:01:32.541 INFO 3324 --- [ool-20-thread-1] c.i.h.c.d.impl.DataDicLocalServiceImpl : 配置的字典编码.size=0 2025-08-06 09:01:32.557 INFO 3324 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat started on port(s): 7099 (http) with context path '' 2025-08-06 09:01:32.574 INFO 3324 --- [ool-20-thread-1] c.i.hsa.common.dict.DataDictManager : 加载字典数=1160 2025-08-06 09:01:33.165 INFO 3324 --- [ main] s.a.ScheduledAnnotationBeanPostProcessor : No TaskScheduler/ScheduledExecutorService bean found for scheduled processing 2025-08-06 09:01:33.173 INFO 3324 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat started on port(s): 9100 (http) with context path '/insiis7-enforce' 2025-08-06 09:01:33.175 INFO 3324 --- [ main] com.insigma.InsiisWebApplication : Started InsiisWebApplication in 57.123 seconds (JVM running for 67.713) 八月 06, 2025 9:01:33 上午 org.apache.coyote.AbstractProtocol start 信息: Starting ProtocolHandler ["http-nio-9100"] 2025-08-06 09:01:33.205 INFO 3324 --- [ main] c.i.b.send.server.init.InitServer : 初始化结果en:false Service(pandora boot) startup in 61482 ms 2025-08-06 09:01:33.786 INFO 3324 --- [ool-21-thread-1] c.i.h.c.region.service.PoolareaManager : 加载统筹区数据! 2025-08-06 09:01:33.908 INFO 3324 --- [ool-21-thread-1] c.i.h.c.region.service.PoolareaManager : 加载和缓存所有统筹区完毕!queryResult.size=4478 2025-08-06 09:01:33.943 INFO 3324 --- [ool-21-thread-1] c.i.h.c.region.service.PoolareaManager : 加载统筹区数据完毕!highest.size=469,groupResult.size=373 Wed Aug 06 09:01:34 CST 2025 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. 八月 06, 2025 9:01:34 上午 org.apache.catalina.core.ApplicationContext log 信息: Initializing Spring DispatcherServlet 'dispatcherServlet' 2025-08-06 09:01:34.244 INFO 3324 --- [)-10.66.242.118] o.s.web.servlet.DispatcherServlet : Initializing Servlet 'dispatcherServlet' 2025-08-06 09:01:34.256 INFO 3324 --- [)-10.66.242.118] o.s.web.servlet.DispatcherServlet : Completed initialization in 12 ms Wed Aug 06 09:01:34 CST 2025 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. Wed Aug 06 09:01:34 CST 2025 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. Wed Aug 06 09:01:34 CST 2025 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. Wed Aug 06 09:01:34 CST 2025 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification. 2025-08-06 09:01:34.363 INFO 3324 --- [)-10.66.242.118] com.alibaba.druid.pool.DruidDataSource : {dataSource-3} inited 2025-08-06 09:01:35.750 INFO 3324 --- [ool-21-thread-1] c.i.h.c.admdvs.bo.impl.AdmdvsBOImpl : 加载行政区划数据... 2025-08-06 09:01:35.778 INFO 3324 --- [ool-21-thread-1] c.i.h.c.admdvs.bo.impl.AdmdvsBOImpl : 行政区划数据缓存完毕!省份数=1,地市数=1,区县数=17 2025-08-06 09:04:28.806 INFO 3324 --- [nio-9100-exec-9] c.i.h.s.w.support.SSOUserContextFilter : in SSOUserContextFilter! securitytype is hsa-sso-mock 2025-08-06 09:04:28.806 INFO 3324 --- [nio-9100-exec-3] c.i.h.s.w.support.SSOUserContextFilter : in SSOUserContextFilter! securitytype is hsa-sso-mock 2025-08-06 09:04:28.806 INFO 3324 --- [nio-9100-exec-1] c.i.h.s.w.support.SSOUserContextFilter : in SSOUserContextFilter! securitytype is hsa-sso-mock 2025-08-06 09:04:28.829 INFO 3324 --- [nio-9100-exec-9] c.i.f.w.s.web.RepeatRequestFilter : ===repeat=false=== 2025-08-06 09:04:28.829 INFO 3324 --- [nio-9100-exec-3] c.i.f.w.s.web.RepeatRequestFilter : ===repeat=false=== 2025-08-06 09:04:28.830 INFO 3324 --- [nio-9100-exec-1] c.i.f.w.s.web.RepeatRequestFilter : ===repeat=false=== Hibernate: select sysmenu0_.functionid as function1_7_, sysmenu0_.active as active2_7_, sysmenu0_.auflag as auflag3_7_, sysmenu0_.description as descript4_7_, sysmenu0_.developer as develope5_7_, sysmenu0_.digest as digest6_7_, sysmenu0_.funcode as funcode7_7_, sysmenu0_.funorder as funorder8_7_, sysmenu0_.funtype as funtype9_7_, sysmenu0_.icon as icon10_7_, sysmenu0_.idpath as idpath11_7_, sysmenu0_.islog as islog12_7_, sysmenu0_.location as locatio13_7_, sysmenu0_.nodetype as nodetyp14_7_, sysmenu0_.parentid as parenti15_7_, sysmenu0_.rbflag as rbflag16_7_, sysmenu0_.slevel as slevel17_7_, sysmenu0_.title as title18_7_ from SYSFUNCTION sysmenu0_ order by sysmenu0_.funorder 2025-08-06 09:04:31.567 INFO 3324 --- [nio-9100-exec-2] c.i.h.s.w.support.SSOUserContextFilter : in SSOUserContextFilter! securitytype is hsa-sso-mock 2025-08-06 09:04:31.569 INFO 3324 --- [nio-9100-exec-2] c.i.f.w.s.web.RepeatRequestFilter : ===repeat=false=== Hibernate: select sysmenu0_.functionid as function1_7_, sysmenu0_.active as active2_7_, sysmenu0_.auflag as auflag3_7_, sysmenu0_.description as descript4_7_, sysmenu0_.developer as develope5_7_, sysmenu0_.digest as digest6_7_, sysmenu0_.funcode as funcode7_7_, sysmenu0_.funorder as funorder8_7_, sysmenu0_.funtype as funtype9_7_, sysmenu0_.icon as icon10_7_, sysmenu0_.idpath as idpath11_7_, sysmenu0_.islog as islog12_7_, sysmenu0_.location as locatio13_7_, sysmenu0_.nodetype as nodetyp14_7_, sysmenu0_.parentid as parenti15_7_, sysmenu0_.rbflag as rbflag16_7_, sysmenu0_.slevel as slevel17_7_, sysmenu0_.title as title18_7_ from SYSFUNCTION sysmenu0_ order by sysmenu0_.funorder 2025-08-06 09:04:31.570 INFO 3324 --- [nio-9100-exec-6] c.i.h.s.w.support.SSOUserContextFilter : in SSOUserContextFilter! securitytype is hsa-sso-mock 2025-08-06 09:04:31.570 INFO 3324 --- [io-9100-exec-10] c.i.h.s.w.support.SSOUserContextFilter : in SSOUserContextFilter! securitytype is hsa-sso-mock 2025-08-06 09:04:31.572 INFO 3324 --- [io-9100-exec-10] c.i.f.w.s.web.RepeatRequestFilter : ===repeat=false=== 2025-08-06 09:04:31.572 INFO 3324 --- [nio-9100-exec-6] c.i.f.w.s.web.RepeatRequestFilter : ===repeat=false=== 为什么运行不结束
08-07
<think>嗯,用户之前询问了关于Java启动参数的问题,特别是涉及`--add-opens`的错误。现在他问的是启动Tomcat时遇到的错误。我需要先确定Tomcat启动错误的常见原因,然后结合之前的对话内容,看看是否有关联。 首先,用户之前的问题是关于JDK版本和参数兼容性,可能Tomcat启动错误也可能与JDK版本不匹配有关。比如,Tomcat 10及以上需要JDK 11或更高,而旧版Tomcat可能需要JDK 8。这时候如果用户使用了错误的JDK版本,就会错。 另外,常见的Tomcat错误还包括端口冲突,比如8080端口被其他程序占用。或者webapps目录下的应用有错误,比如缺少依赖库,或者配置文件如server.xml、web.xml有语法错误。还有权限问题,比如在Linux下没有执行权限,或者文件所有权不正确。 内存设置也可能导致启动失败,比如PermGen空间不足,这时候需要调整JVM参数,如-XX:MaxPermSize或-XX:MaxMetaspaceSize。不过根据用户之前的提问,可能已经处理过这部分,但需要确认是否正确应用到了Tomcat的启动脚本中。 还有类冲突或版本不兼容,比如项目中使用了与Tomcat内置库冲突的jar包,比如Servlet API的不同版本。此外,日志文件是重要的排查工具,需要查看catalina.out或localhost.log中的具体错误信息。 用户可能没有提供具体的错误信息,所以需要引导他检查日志,确认错误类型。比如常见的ClassNotFoundException、NoSuchMethodError,或者SEVERE级别的启动错误。然后根据不同的错误类型给出对应的解决方案。 还需要考虑环境变量是否正确设置,比如JAVA_HOME是否指向正确的JDK路径,CATALINA_HOME是否设置正确。另外,检查Tomcat的安装是否完整,是否有损坏的文件。 总结一下,可能的回复步骤包括:确认错误日志内容,检查JDK版本兼容性,端口占用情况,内存参数设置,配置文件正确性,依赖库冲突,以及权限问题。需要分步骤引导用户逐一排查,并给出具体的命令或检查方法,比如用netstat检查端口,用ps查看进程,或者如何调整JVM参数等。</think>以下是针对 **Tomcat 启动错** 的通用排查指南,按优先级排序: --- ### **1. 查看错误日志(关键!)** Tomcat 日志路径:`$CATALINA_HOME/logs/catalina.out` 或 `localhost.log` 执行以下命令查看实时日志: ```bash tail -f $CATALINA_HOME/logs/catalina.out ``` - **定位错误类型**:如 `ClassNotFoundException`、`NoSuchMethodError`、端口占用、权限问题等。 --- ### **2. 常见错误类型及解决方案** #### **2.1 端口冲突(最常见)** - **错误提示**:`Address already in use: JVM_Bind` 或 `Port 8080 is already in use` - **解决步骤**: 1. 查找占用端口的进程: ```bash # Linux/Mac lsof -i :8080 # Windows netstat -ano | findstr "8080" ``` 2. 关闭占用进程,或修改 Tomcat 端口(编辑 `$CATALINA_HOME/conf/server.xml`): ```xml <Connector port="8080" protocol="HTTP/1.1" ... /> ``` #### **2.2 JDK 版本不兼容** - **错误提示**:`Unsupported major.minor version` 或 `javax.servlet 不存在` - **原因**:Tomcat 版本与 JDK 不匹配。 - **对照表**: | Tomcat 版本 | 要求 JDK 版本 | |-------------|---------------| | Tomcat 10.x | JDK 11+ | | Tomcat 9.x | JDK 8+ | | Tomcat 8.x | JDK 7+ | - **检查 JDK**: ```bash java -version ``` #### **2.3 内存不足(PermGen/Metaspace)** - **错误提示**:`java.lang.OutOfMemoryError: PermGen space` 或 `Metaspace` - **解决**:在 `$CATALINA_HOME/bin/catalina.sh`(Linux/Mac)或 `catalina.bat`(Windows)中添加 JVM 参数: ```bash # JDK 8 及之前 export JAVA_OPTS="-XX:PermSize=256m -XX:MaxPermSize=512m" # JDK 8 之后 export JAVA_OPTS="-XX:MaxMetaspaceSize=512m" ``` #### **2.4 应用部署失败** - **错误提示**:`FAIL - Application at context path [/xxx] could not be started` - **原因**:Web 应用(如 WAR 包)存在配置或代码问题。 - **排查**: 1. 检查 `webapps/xxx/WEB-INF/classes` 下的配置文件(如 `web.xml`)。 2. 确认依赖库(`WEB-INF/lib`)无冲突或缺失。 #### **2.5 权限问题(Linux/Mac)** - **错误提示**:`Permission denied` - **解决**: ```bash chmod +x $CATALINA_HOME/bin/*.sh chown -R 用户名:用户组 $CATALINA_HOME ``` --- ### **3. 快速验证 Tomcat 基础功能** 1. 清空 `webapps` 目录(备份后删除所有文件)。 2. 启动 Tomcat: ```bash $CATALINA_HOME/bin/startup.sh ``` - 若仍失败,说明问题在 Tomcat 自身配置或环境。 - 若成功,逐步恢复应用 WAR 包,定位具体应用问题。 --- ### **4. 附:Tomcat 关键文件说明** | 文件/目录 | 作用 | |--------------------------|--------------------------| | `conf/server.xml` | 配置端口、连接器等 | | `conf/web.xml` | 全局 Servlet 配置 | | `webapps/` | 存放部署的 WAR 包或应用 | | `bin/startup.sh` | 启动脚本 | | `logs/catalina.out` | 核心日志 | --- 如果问题仍未解决,请提供 **具体错误日志片段**,以便进一步分析!
评论 1
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值