Avue-Data大屏一直显示加载中

Blade 未结 1 145
hotwind
hotwind 剑童 2025-09-24 19:41
悬赏:5

一、该问题的重现步骤是什么?

1. 安装Avue-Data的教程进行操作;配置好lisence.js、.npmrc。

2. src/config.js按照如下进行配置:
image.png

3.后端data-server-boot中resources的application.yml文件的端口号如下

port: 8060

数据库也正常配置。
image.png

mysql连接正常。

4但是一直出现加载中image.png

avue-ec6b14c7.js:7  GET http://10.67.11.203:8060/blade-visual/db/list?current=1&size=10 net::ERR_CONNECTION_REFUSED

而且redis数据库里没有数据。


二、你期待的结果是什么?实际看到的又是什么?


三、你正在使用的是什么产品,什么版本?在什么操作系统上?


四、请提供详细的错误堆栈信息,这很重要。


五、若有更多详细信息,请在下面提供。

1条回答
  • 2025-09-24 21:22

    你单独访问 http://10.67.11.203:8060/blade-visual/db/list?current=1&size=10  这个地址,看看返回什么信息,然后后端的详细日志是什么,看看后端有没有报错。

    作者追问:2025-09-25 08:50

    image.png

    Sep 24 19:09:46 localhost spring_bladex_visual_jar: ----启动中,读取到的环境变量:[prod],jar地址:[nested:/www/wwwroot/10.67.11.203_2333/api/bladex-visual.jar/]----
    Sep 24 19:09:48 localhost spring_bladex_visual_jar: ____  _           _     __   __  _____        _           _____
    Sep 24 19:09:48 localhost spring_bladex_visual_jar: |  _ \| |         | |    \ \ / / |  __ \      | |         / ____|
    Sep 24 19:09:48 localhost spring_bladex_visual_jar: | |_) | | __ _  __| | ___ \ V /  | |  | | __ _| |_ __ _  | (___   ___ _ ____   _____ _ __
    Sep 24 19:09:48 localhost spring_bladex_visual_jar: |  _ <| |/ _` |/ _` |/ _ \ > <   | |  | |/ _` | __/ _` |  \___ \ / _ \ '__\ \ / / _ \ '__|
    Sep 24 19:09:48 localhost spring_bladex_visual_jar: | |_) | | (_| | (_| |  __// . \  | |__| | (_| | || (_| |  ____) |  __/ |   \ V /  __/ |
    Sep 24 19:09:48 localhost spring_bladex_visual_jar: |____/|_|\__,_|\__,_|\___/_/ \_\ |_____/ \__,_|\__\__,_| |_____/ \___|_|    \_/ \___|_|
    Sep 24 19:09:48 localhost spring_bladex_visual_jar: :: DataServer :: blade-data-server:prod :: Running SpringBoot 3.2.12 ::
    Sep 24 19:09:48 localhost spring_bladex_visual_jar: 2025-09-24 19:09:48.223  INFO 14419 --- [kground-preinit] o.h.validator.internal.util.Version      : HV000001: Hibernate Validator 8.0.1.Final
    Sep 24 19:09:48 localhost spring_bladex_visual_jar: 2025-09-24 19:09:48.498  INFO 14419 --- [           main] org.springblade.Application              : Starting Application using Java 17.0.8 with PID 14419 (/www/wwwroot/10.67.11.203_2333/api/bladex-visual.jar started by www in /www/wwwroot/10.67.11.203_2333/api)
    Sep 24 19:09:48 localhost spring_bladex_visual_jar: 2025-09-24 19:09:48.499  INFO 14419 --- [           main] org.springblade.Application              : The following 1 profile is active: "prod"
    Sep 24 19:09:50 localhost spring_bladex_visual_jar: 2025-09-24 19:09:50.913  INFO 14419 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Multiple Spring Data modules found, entering strict repository configuration mode
    Sep 24 19:09:50 localhost spring_bladex_visual_jar: 2025-09-24 19:09:50.916  INFO 14419 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data Redis repositories in DEFAULT mode.
    Sep 24 19:09:51 localhost spring_bladex_visual_jar: 2025-09-24 19:09:51.010  INFO 14419 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 72 ms. Found 0 Redis repository interfaces.
    Sep 24 19:09:51 localhost spring_bladex_visual_jar: 2025-09-24 19:09:51.168  WARN 14419 --- [           main] o.m.s.mapper.ClassPathMapperScanner      : No MyBatis mapper was found in '[org.springblade]' package. Please check your configuration.
    Sep 24 19:09:51 localhost spring_bladex_visual_jar: 2025-09-24 19:09:51.328  INFO 14419 --- [           main] o.s.cloud.context.scope.GenericScope     : BeanFactory id=975a0734-721a-3a17-9553-693a25c93ba5
    Sep 24 19:09:51 localhost spring_bladex_visual_jar: 2025-09-24 19:09:51.334  INFO 14419 --- [           main] s.c.l.p.BladePropertySourcePostProcessor : BladePropertySourcePostProcessor init.
    Sep 24 19:09:51 localhost spring_bladex_visual_jar: 2025-09-24 19:09:51.404  INFO 14419 --- [           main] s.c.l.p.BladePropertySourcePostProcessor : BladePropertySourcePostProcessor process @BladePropertySource bean.
    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.001  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springblade.core.redis.config.RedisPubSubConfiguration' of type [org.springblade.core.redis.config.RedisPubSubConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). The currently created BeanPostProcessor [topicListenerDetector] is declared through a non-static factory method on that class; consider declaring it as static instead.
    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.029  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'spring.data.redis-org.springframework.boot.autoconfigure.data.redis.RedisProperties' of type [org.springframework.boot.autoconfigure.data.redis.RedisProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.039  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.data.redis.RedisAutoConfiguration' of type [org.springframework.boot.autoconfigure.data.redis.RedisAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.046  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'redisConnectionDetails' of type [org.springframework.boot.autoconfigure.data.redis.PropertiesRedisConnectionDetails] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.058  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'spring.ssl-org.springframework.boot.autoconfigure.ssl.SslProperties' of type [org.springframework.boot.autoconfigure.ssl.SslProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.060  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.ssl.SslAutoConfiguration' of type [org.springframework.boot.autoconfigure.ssl.SslAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.069  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'fileWatcher' of type [org.springframework.boot.autoconfigure.ssl.FileWatcher] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.073  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'sslPropertiesSslBundleRegistrar' of type [org.springframework.boot.autoconfigure.ssl.SslPropertiesBundleRegistrar] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.085  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'sslBundleRegistry' of type [org.springframework.boot.ssl.DefaultSslBundleRegistry] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.089  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.data.redis.LettuceConnectionConfiguration' of type [org.springframework.boot.autoconfigure.data.redis.LettuceConnectionConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.135  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.actuate.autoconfigure.metrics.redis.LettuceMetricsAutoConfiguration' of type [org.springframework.boot.actuate.autoconfigure.metrics.redis.LettuceMetricsAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.144  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.actuate.autoconfigure.metrics.export.simple.SimpleMetricsExportAutoConfiguration' of type [org.springframework.boot.actuate.autoconfigure.metrics.export.simple.SimpleMetricsExportAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.150  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'management.simple.metrics.export-org.springframework.boot.actuate.autoconfigure.metrics.export.simple.SimpleProperties' of type [org.springframework.boot.actuate.autoconfigure.metrics.export.simple.SimpleProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.163  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'simpleConfig' of type [org.springframework.boot.actuate.autoconfigure.metrics.export.simple.SimplePropertiesConfigAdapter] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.171  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.actuate.autoconfigure.metrics.MetricsAutoConfiguration' of type [org.springframework.boot.actuate.autoconfigure.metrics.MetricsAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.186  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'micrometerClock' of type [io.micrometer.core.instrument.Clock$1] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.225  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'simpleMeterRegistry' of type [io.micrometer.core.instrument.simple.SimpleMeterRegistry] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.259  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'micrometerOptions' of type [io.lettuce.core.metrics.MicrometerOptions] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.263  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'lettuceMetrics' of type [org.springframework.boot.actuate.autoconfigure.metrics.redis.LettuceMetricsAutoConfiguration$$Lambda$754/0x00007f5b1453c9f8] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.371  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'lettuceClientResources' of type [io.lettuce.core.resource.DefaultClientResources] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.487  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'redisConnectionFactory' of type [org.springframework.data.redis.connection.lettuce.LettuceConnectionFactory] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.514  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'redisMessageListenerContainer' of type [org.springframework.data.redis.listener.RedisMessageListenerContainer] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.527  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springblade.core.redis.config.ProtoStuffSerializerConfiguration' of type [org.springblade.core.redis.config.ProtoStuffSerializerConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.580  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'redisSerializer' of type [org.springblade.core.redis.serializer.ProtoStuffSerializer] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.
    Sep 24 19:09:53 localhost spring_bladex_visual_jar: 2025-09-24 19:09:53.007  WARN 14419 --- [           main] io.undertow.websockets.jsr               : UT026010: Buffer pool was not set on WebSocketDeploymentInfo, the default pool will be used
    Sep 24 19:09:53 localhost spring_bladex_visual_jar: 2025-09-24 19:09:53.033  INFO 14419 --- [           main] io.undertow.servlet                      : Initializing Spring embedded WebApplicationContext
    Sep 24 19:09:53 localhost spring_bladex_visual_jar: 2025-09-24 19:09:53.033  INFO 14419 --- [           main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 4369 ms
    Sep 24 19:09:53 localhost spring_bladex_visual_jar: 2025-09-24 19:09:53.482  INFO 14419 --- [           main] c.b.d.d.p.AbstractJdbcDataSourceProvider : 成功加载数据库驱动程序
    Sep 24 19:09:53 localhost spring_bladex_visual_jar: 2025-09-24 19:09:53.822  INFO 14419 --- [           main] c.b.d.d.p.AbstractJdbcDataSourceProvider : 成功获取数据库连接
    Sep 24 19:09:53 localhost spring_bladex_visual_jar: 2025-09-24 19:09:53.975  INFO 14419 --- [           main] com.alibaba.druid.pool.DruidDataSource   : {dataSource-1,master} inited
    Sep 24 19:09:53 localhost spring_bladex_visual_jar: 2025-09-24 19:09:53.986  INFO 14419 --- [           main] c.b.d.d.DynamicRoutingDataSource         : dynamic-datasource - add a datasource named [master] success
    Sep 24 19:09:53 localhost spring_bladex_visual_jar: 2025-09-24 19:09:53.987  INFO 14419 --- [           main] c.b.d.d.DynamicRoutingDataSource         : dynamic-datasource initial loaded [1] datasource,primary datasource named [master]
    Sep 24 19:09:54 localhost spring_bladex_visual_jar: _ _   |_  _ _|_. ___ _ |    _
    Sep 24 19:09:54 localhost spring_bladex_visual_jar: | | |\/|_)(_| | |_\  |_)||_|_\
    Sep 24 19:09:54 localhost spring_bladex_visual_jar: /               |
    Sep 24 19:09:54 localhost spring_bladex_visual_jar: 3.5.8
    Sep 24 19:10:37 localhost spring_bladex_visual_jar: 2025-09-24 19:10:37.864  INFO 14419 --- [           main] o.s.core.boot.config.RetryConfiguration  : configServerRetryInterceptor: Changing backOffOptions to initial: 1000, multiplier: 1.2, maxInterval: 5000
    Sep 24 19:10:37 localhost spring_bladex_visual_jar: 2025-09-24 19:10:37.884  INFO 14419 --- [           main] f.a.AutowiredAnnotationBeanPostProcessor : Inconsistent constructor declaration on bean with name 'org.springblade.core.launch.server.ServerInfo': single autowire-marked constructor flagged as optional - this constructor is effectively required since there is no default constructor to fall back to: public org.springblade.core.launch.server.ServerInfo(org.springframework.boot.autoconfigure.web.ServerProperties)
    Sep 24 19:10:37 localhost spring_bladex_visual_jar: 2025-09-24 19:10:37.904  INFO 14419 --- [           main] o.s.core.log.logger.BladeLogger          : blade-data-server: BladeLogger init success!
    Sep 24 19:10:38 localhost spring_bladex_visual_jar: 2025-09-24 19:10:38.157  INFO 14419 --- [           main] o.s.c.redis.pubsub.RedisPubSubPublisher  : RPubSubPublisher init success.
    Sep 24 19:10:39 localhost spring_bladex_visual_jar: 2025-09-24 19:10:38.999  INFO 14419 --- [           main] o.s.b.a.e.web.EndpointLinksResolver      : Exposing 1 endpoint(s) beneath base path '/actuator'
    Sep 24 19:10:39 localhost spring_bladex_visual_jar: 2025-09-24 19:10:39.092  INFO 14419 --- [           main] io.undertow                              : starting server: Undertow - 2.3.17.Final
    Sep 24 19:10:39 localhost spring_bladex_visual_jar: 2025-09-24 19:10:39.104  INFO 14419 --- [           main] org.xnio                                 : XNIO version 3.8.16.Final
    Sep 24 19:10:39 localhost spring_bladex_visual_jar: 2025-09-24 19:10:39.116  INFO 14419 --- [           main] org.xnio.nio                             : XNIO NIO Implementation Version 3.8.16.Final
    Sep 24 19:10:39 localhost spring_bladex_visual_jar: 2025-09-24 19:10:39.145  INFO 14419 --- [           main] org.jboss.threads                        : JBoss Threads version 3.5.0.Final
    Sep 24 19:10:39 localhost spring_bladex_visual_jar: 2025-09-24 19:10:39.190  INFO 14419 --- [           main] o.s.b.w.e.undertow.UndertowWebServer     : Undertow started on port 8060 (http)
    Sep 24 19:10:39 localhost spring_bladex_visual_jar: 2025-09-24 19:10:39.214  INFO 14419 --- [sync-executor-1] o.s.core.launch.StartEventListener       : ---[BLADE-DATA-SERVER]---启动完成,当前使用的端口:[8060],环境变量:[prod]---
    Sep 24 19:10:39 localhost spring_bladex_visual_jar: 2025-09-24 19:10:39.236  INFO 14419 --- [           main] org.springblade.Application              : Started Application in 52.236 seconds (process running for 53.394)
    Sep 25 08:43:57 localhost spring_bladex_visual_jar: 2025-09-25 08:43:57.787  INFO 14419 --- [  XNIO-1 task-2] io.undertow.servlet                      : Initializing Spring DispatcherServlet 'dispatcherServlet'
    Sep 25 08:43:57 localhost spring_bladex_visual_jar: 2025-09-25 08:43:57.800  INFO 14419 --- [  XNIO-1 task-2] o.s.web.servlet.DispatcherServlet        : Initializing Servlet 'dispatcherServlet'
    Sep 25 08:43:57 localhost spring_bladex_visual_jar: 2025-09-25 08:43:57.820  INFO 14419 --- [  XNIO-1 task-2] o.s.web.servlet.DispatcherServlet        : Completed initialization in 20 ms
    Sep 25 08:43:58 localhost spring_bladex_visual_jar: 2025-09-25 08:43:58.990  WARN 14419 --- [  XNIO-1 task-3] o.s.c.s.interceptor.SecureInterceptor    : 签名认证失败,请求接口:/favicon.ico,请求IP:10.67.84.10,请求参数:{}

    本机ip地址为 :

    10.67.84.10



    作者追问:2025-09-25 08:52

    Sep 24 19:09:46 localhost spring_bladex_visual_jar: ----启动中,读取到的环境变量:[prod],jar地址:[nested:/www/wwwroot/10.67.11.203_2333/api/bladex-visual.jar/]----

    Sep 24 19:09:48 localhost spring_bladex_visual_jar: ____  _           _     __   __  _____        _           _____

    Sep 24 19:09:48 localhost spring_bladex_visual_jar: |  _ \| |         | |    \ \ / / |  __ \      | |         / ____|

    Sep 24 19:09:48 localhost spring_bladex_visual_jar: | |_) | | __ _  __| | ___ \ V /  | |  | | __ _| |_ __ _  | (___   ___ _ ____   _____ _ __

    Sep 24 19:09:48 localhost spring_bladex_visual_jar: |  _ <| |/ _` |/ _` |/ _ \ > <   | |  | |/ _` | __/ _` |  \___ \ / _ \ '__\ \ / / _ \ '__|

    Sep 24 19:09:48 localhost spring_bladex_visual_jar: | |_) | | (_| | (_| |  __// . \  | |__| | (_| | || (_| |  ____) |  __/ |   \ V /  __/ |

    Sep 24 19:09:48 localhost spring_bladex_visual_jar: |____/|_|\__,_|\__,_|\___/_/ \_\ |_____/ \__,_|\__\__,_| |_____/ \___|_|    \_/ \___|_|

    Sep 24 19:09:48 localhost spring_bladex_visual_jar: :: DataServer :: blade-data-server:prod :: Running SpringBoot 3.2.12 ::

    Sep 24 19:09:48 localhost spring_bladex_visual_jar: 2025-09-24 19:09:48.223  INFO 14419 --- [kground-preinit] o.h.validator.internal.util.Version      : HV000001: Hibernate Validator 8.0.1.Final

    Sep 24 19:09:48 localhost spring_bladex_visual_jar: 2025-09-24 19:09:48.498  INFO 14419 --- [           main] org.springblade.Application              : Starting Application using Java 17.0.8 with PID 14419 (/www/wwwroot/10.67.11.203_2333/api/bladex-visual.jar started by www in /www/wwwroot/10.67.11.203_2333/api)

    Sep 24 19:09:48 localhost spring_bladex_visual_jar: 2025-09-24 19:09:48.499  INFO 14419 --- [           main] org.springblade.Application              : The following 1 profile is active: "prod"

    Sep 24 19:09:50 localhost spring_bladex_visual_jar: 2025-09-24 19:09:50.913  INFO 14419 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Multiple Spring Data modules found, entering strict repository configuration mode

    Sep 24 19:09:50 localhost spring_bladex_visual_jar: 2025-09-24 19:09:50.916  INFO 14419 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data Redis repositories in DEFAULT mode.

    Sep 24 19:09:51 localhost spring_bladex_visual_jar: 2025-09-24 19:09:51.010  INFO 14419 --- [           main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 72 ms. Found 0 Redis repository interfaces.

    Sep 24 19:09:51 localhost spring_bladex_visual_jar: 2025-09-24 19:09:51.168  WARN 14419 --- [           main] o.m.s.mapper.ClassPathMapperScanner      : No MyBatis mapper was found in '[org.springblade]' package. Please check your configuration.

    Sep 24 19:09:51 localhost spring_bladex_visual_jar: 2025-09-24 19:09:51.328  INFO 14419 --- [           main] o.s.cloud.context.scope.GenericScope     : BeanFactory id=975a0734-721a-3a17-9553-693a25c93ba5

    Sep 24 19:09:51 localhost spring_bladex_visual_jar: 2025-09-24 19:09:51.334  INFO 14419 --- [           main] s.c.l.p.BladePropertySourcePostProcessor : BladePropertySourcePostProcessor init.

    Sep 24 19:09:51 localhost spring_bladex_visual_jar: 2025-09-24 19:09:51.404  INFO 14419 --- [           main] s.c.l.p.BladePropertySourcePostProcessor : BladePropertySourcePostProcessor process @BladePropertySource bean.

    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.001  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springblade.core.redis.config.RedisPubSubConfiguration' of type [org.springblade.core.redis.config.RedisPubSubConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). The currently created BeanPostProcessor [topicListenerDetector] is declared through a non-static factory method on that class; consider declaring it as static instead.

    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.029  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'spring.data.redis-org.springframework.boot.autoconfigure.data.redis.RedisProperties' of type [org.springframework.boot.autoconfigure.data.redis.RedisProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.

    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.039  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.data.redis.RedisAutoConfiguration' of type [org.springframework.boot.autoconfigure.data.redis.RedisAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.

    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.046  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'redisConnectionDetails' of type [org.springframework.boot.autoconfigure.data.redis.PropertiesRedisConnectionDetails] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.

    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.058  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'spring.ssl-org.springframework.boot.autoconfigure.ssl.SslProperties' of type [org.springframework.boot.autoconfigure.ssl.SslProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.

    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.060  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.ssl.SslAutoConfiguration' of type [org.springframework.boot.autoconfigure.ssl.SslAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.

    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.069  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'fileWatcher' of type [org.springframework.boot.autoconfigure.ssl.FileWatcher] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.

    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.073  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'sslPropertiesSslBundleRegistrar' of type [org.springframework.boot.autoconfigure.ssl.SslPropertiesBundleRegistrar] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.

    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.085  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'sslBundleRegistry' of type [org.springframework.boot.ssl.DefaultSslBundleRegistry] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.

    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.089  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.autoconfigure.data.redis.LettuceConnectionConfiguration' of type [org.springframework.boot.autoconfigure.data.redis.LettuceConnectionConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.

    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.135  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.actuate.autoconfigure.metrics.redis.LettuceMetricsAutoConfiguration' of type [org.springframework.boot.actuate.autoconfigure.metrics.redis.LettuceMetricsAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.

    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.144  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.actuate.autoconfigure.metrics.export.simple.SimpleMetricsExportAutoConfiguration' of type [org.springframework.boot.actuate.autoconfigure.metrics.export.simple.SimpleMetricsExportAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.

    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.150  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'management.simple.metrics.export-org.springframework.boot.actuate.autoconfigure.metrics.export.simple.SimpleProperties' of type [org.springframework.boot.actuate.autoconfigure.metrics.export.simple.SimpleProperties] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.

    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.163  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'simpleConfig' of type [org.springframework.boot.actuate.autoconfigure.metrics.export.simple.SimplePropertiesConfigAdapter] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.

    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.171  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.boot.actuate.autoconfigure.metrics.MetricsAutoConfiguration' of type [org.springframework.boot.actuate.autoconfigure.metrics.MetricsAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.

    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.186  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'micrometerClock' of type [io.micrometer.core.instrument.Clock$1] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.

    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.225  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'simpleMeterRegistry' of type [io.micrometer.core.instrument.simple.SimpleMeterRegistry] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.

    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.259  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'micrometerOptions' of type [io.lettuce.core.metrics.MicrometerOptions] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.

    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.263  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'lettuceMetrics' of type [org.springframework.boot.actuate.autoconfigure.metrics.redis.LettuceMetricsAutoConfiguration$$Lambda$754/0x00007f5b1453c9f8] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.

    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.371  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'lettuceClientResources' of type [io.lettuce.core.resource.DefaultClientResources] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.

    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.487  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'redisConnectionFactory' of type [org.springframework.data.redis.connection.lettuce.LettuceConnectionFactory] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.

    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.514  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'redisMessageListenerContainer' of type [org.springframework.data.redis.listener.RedisMessageListenerContainer] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.

    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.527  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springblade.core.redis.config.ProtoStuffSerializerConfiguration' of type [org.springblade.core.redis.config.ProtoStuffSerializerConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.

    Sep 24 19:09:52 localhost spring_bladex_visual_jar: 2025-09-24 19:09:52.580  WARN 14419 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'redisSerializer' of type [org.springblade.core.redis.serializer.ProtoStuffSerializer] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying). Is this bean getting eagerly injected/applied to a currently created BeanPostProcessor [topicListenerDetector]? Check the corresponding BeanPostProcessor declaration and its dependencies/advisors. If this bean does not have to be post-processed, declare it with ROLE_INFRASTRUCTURE.

    Sep 24 19:09:53 localhost spring_bladex_visual_jar: 2025-09-24 19:09:53.007  WARN 14419 --- [           main] io.undertow.websockets.jsr               : UT026010: Buffer pool was not set on WebSocketDeploymentInfo, the default pool will be used

    Sep 24 19:09:53 localhost spring_bladex_visual_jar: 2025-09-24 19:09:53.033  INFO 14419 --- [           main] io.undertow.servlet                      : Initializing Spring embedded WebApplicationContext

    Sep 24 19:09:53 localhost spring_bladex_visual_jar: 2025-09-24 19:09:53.033  INFO 14419 --- [           main] w.s.c.ServletWebServerApplicationContext : Root WebApplicationContext: initialization completed in 4369 ms

    Sep 24 19:09:53 localhost spring_bladex_visual_jar: 2025-09-24 19:09:53.482  INFO 14419 --- [           main] c.b.d.d.p.AbstractJdbcDataSourceProvider : 成功加载数据库驱动程序

    Sep 24 19:09:53 localhost spring_bladex_visual_jar: 2025-09-24 19:09:53.822  INFO 14419 --- [           main] c.b.d.d.p.AbstractJdbcDataSourceProvider : 成功获取数据库连接

    Sep 24 19:09:53 localhost spring_bladex_visual_jar: 2025-09-24 19:09:53.975  INFO 14419 --- [           main] com.alibaba.druid.pool.DruidDataSource   : {dataSource-1,master} inited

    Sep 24 19:09:53 localhost spring_bladex_visual_jar: 2025-09-24 19:09:53.986  INFO 14419 --- [           main] c.b.d.d.DynamicRoutingDataSource         : dynamic-datasource - add a datasource named [master] success

    Sep 24 19:09:53 localhost spring_bladex_visual_jar: 2025-09-24 19:09:53.987  INFO 14419 --- [           main] c.b.d.d.DynamicRoutingDataSource         : dynamic-datasource initial loaded [1] datasource,primary datasource named [master]

    Sep 24 19:09:54 localhost spring_bladex_visual_jar: _ _   |_  _ _|_. ___ _ |    _

    Sep 24 19:09:54 localhost spring_bladex_visual_jar: | | |\/|_)(_| | |_\  |_)||_|_\

    Sep 24 19:09:54 localhost spring_bladex_visual_jar: /               |

    Sep 24 19:09:54 localhost spring_bladex_visual_jar: 3.5.8

    Sep 24 19:10:37 localhost spring_bladex_visual_jar: 2025-09-24 19:10:37.864  INFO 14419 --- [           main] o.s.core.boot.config.RetryConfiguration  : configServerRetryInterceptor: Changing backOffOptions to initial: 1000, multiplier: 1.2, maxInterval: 5000

    Sep 24 19:10:37 localhost spring_bladex_visual_jar: 2025-09-24 19:10:37.884  INFO 14419 --- [           main] f.a.AutowiredAnnotationBeanPostProcessor : Inconsistent constructor declaration on bean with name 'org.springblade.core.launch.server.ServerInfo': single autowire-marked constructor flagged as optional - this constructor is effectively required since there is no default constructor to fall back to: public org.springblade.core.launch.server.ServerInfo(org.springframework.boot.autoconfigure.web.ServerProperties)

    Sep 24 19:10:37 localhost spring_bladex_visual_jar: 2025-09-24 19:10:37.904  INFO 14419 --- [           main] o.s.core.log.logger.BladeLogger          : blade-data-server: BladeLogger init success!

    Sep 24 19:10:38 localhost spring_bladex_visual_jar: 2025-09-24 19:10:38.157  INFO 14419 --- [           main] o.s.c.redis.pubsub.RedisPubSubPublisher  : RPubSubPublisher init success.

    Sep 24 19:10:39 localhost spring_bladex_visual_jar: 2025-09-24 19:10:38.999  INFO 14419 --- [           main] o.s.b.a.e.web.EndpointLinksResolver      : Exposing 1 endpoint(s) beneath base path '/actuator'

    Sep 24 19:10:39 localhost spring_bladex_visual_jar: 2025-09-24 19:10:39.092  INFO 14419 --- [           main] io.undertow                              : starting server: Undertow - 2.3.17.Final

    Sep 24 19:10:39 localhost spring_bladex_visual_jar: 2025-09-24 19:10:39.104  INFO 14419 --- [           main] org.xnio                                 : XNIO version 3.8.16.Final

    Sep 24 19:10:39 localhost spring_bladex_visual_jar: 2025-09-24 19:10:39.116  INFO 14419 --- [           main] org.xnio.nio                             : XNIO NIO Implementation Version 3.8.16.Final

    Sep 24 19:10:39 localhost spring_bladex_visual_jar: 2025-09-24 19:10:39.145  INFO 14419 --- [           main] org.jboss.threads                        : JBoss Threads version 3.5.0.Final

    Sep 24 19:10:39 localhost spring_bladex_visual_jar: 2025-09-24 19:10:39.190  INFO 14419 --- [           main] o.s.b.w.e.undertow.UndertowWebServer     : Undertow started on port 8060 (http)

    Sep 24 19:10:39 localhost spring_bladex_visual_jar: 2025-09-24 19:10:39.214  INFO 14419 --- [sync-executor-1] o.s.core.launch.StartEventListener       : ---[BLADE-DATA-SERVER]---启动完成,当前使用的端口:[8060],环境变量:[prod]---

    Sep 24 19:10:39 localhost spring_bladex_visual_jar: 2025-09-24 19:10:39.236  INFO 14419 --- [           main] org.springblade.Application              : Started Application in 52.236 seconds (process running for 53.394)

    Sep 25 08:43:57 localhost spring_bladex_visual_jar: 2025-09-25 08:43:57.787  INFO 14419 --- [  XNIO-1 task-2] io.undertow.servlet                      : Initializing Spring DispatcherServlet 'dispatcherServlet'

    Sep 25 08:43:57 localhost spring_bladex_visual_jar: 2025-09-25 08:43:57.800  INFO 14419 --- [  XNIO-1 task-2] o.s.web.servlet.DispatcherServlet        : Initializing Servlet 'dispatcherServlet'

    Sep 25 08:43:57 localhost spring_bladex_visual_jar: 2025-09-25 08:43:57.820  INFO 14419 --- [  XNIO-1 task-2] o.s.web.servlet.DispatcherServlet        : Completed initialization in 20 ms

    Sep 25 08:43:58 localhost spring_bladex_visual_jar: 2025-09-25 08:43:58.990  WARN 14419 --- [  XNIO-1 task-3] o.s.c.s.interceptor.SecureInterceptor    : 签名认证失败,请求接口:/favicon.ico,请求IP:10.67.84.10,请求参数:{}

    本机地址为10.67.84.10

    0 讨论(0)
提交回复