Skip to content

yangxiujun / paidan_demo

Go to a project
Commit e54ad13a by yangxiujun
Options

fix: pom update

1 parent 9d4da5ca
Expand all
Inline Side-by-side
Showing with 97 additions and 0 deletions
logs/project-dispatch/error/project-dispatch.error.log 0 → 100644
This diff could not be displayed because it is too large.
logs/project-dispatch/info/project-dispatch.info.log 0 → 100644
This diff could not be displayed because it is too large.
logs/project-dispatch/warn/project-dispatch.warn.log 0 → 100644
2023-12-27 16:14:33.202 [Thread-1] WARN - [HttpClientBeanHolder] Start destroying common HttpClient
2023-12-27 16:14:33.202 [Thread-6] WARN - [NotifyCenter] Start destroying Publisher
2023-12-27 16:14:33.258 [Thread-6] WARN - [NotifyCenter] Destruction of the end
2023-12-27 16:14:33.277 [Thread-1] WARN - [HttpClientBeanHolder] Destruction of the end
logs/project-gateway/error/project-gateway.error.log 0 → 100644
2023-12-25 10:48:47.210 [boundedElastic-1] ERROR - /pea-user/login 访问网关异常:[org.springframework.cloud.gateway.support.NotFoundException.create(NotFoundException.java:45)] 503 SERVICE_UNAVAILABLE "Unable to find instance for project-user"
2023-12-25 10:48:52.078 [boundedElastic-1] ERROR - /pea-user/login 访问网关异常:[org.springframework.cloud.gateway.support.NotFoundException.create(NotFoundException.java:45)] 503 SERVICE_UNAVAILABLE "Unable to find instance for project-user"
2023-12-25 10:49:10.210 [boundedElastic-1] ERROR - /pea-user/login 访问网关异常:[org.springframework.cloud.gateway.support.NotFoundException.create(NotFoundException.java:45)] 503 SERVICE_UNAVAILABLE "Unable to find instance for project-user"
2023-12-25 10:49:24.353 [boundedElastic-1] ERROR - /pea-user/login 访问网关异常:[org.springframework.cloud.gateway.support.NotFoundException.create(NotFoundException.java:45)] 503 SERVICE_UNAVAILABLE "Unable to find instance for project-user"
logs/project-gateway/info/project-gateway.info.log 0 → 100644
2023-12-28 16:59:48.470 [main] INFO - Starting Application using Java 11.0.21 on DESKTOP-B63Q1LT with PID 32644 (D:\yangxiujun\boxi_demo\project-gateway\target\classes started by admin in D:\yangxiujun\boxi_demo)
2023-12-28 16:59:48.496 [main] INFO - The following 1 profile is active: "dev"
2023-12-28 16:59:48.595 [main] INFO - [Nacos Config] Load config[dataId=redis-config.yaml, group=project] success
2023-12-28 16:59:48.598 [main] INFO - [Nacos Config] Load config[dataId=project-gateway.yaml, group=project] success
2023-12-28 16:59:50.974 [main] INFO - Multiple Spring Data modules found, entering strict repository configuration mode
2023-12-28 16:59:50.979 [main] INFO - Bootstrapping Spring Data Redis repositories in DEFAULT mode.
2023-12-28 16:59:51.029 [main] INFO - Finished Spring Data repository scanning in 11 ms. Found 0 Redis repository interfaces.
2023-12-28 16:59:51.451 [main] INFO - BeanFactory id=705273c4-9ee7-3a3d-a0ac-6a6e2ab211de
2023-12-28 16:59:51.956 [main] INFO - Bean 'org.springframework.cloud.client.loadbalancer.reactive.LoadBalancerBeanPostProcessorAutoConfiguration' of type [org.springframework.cloud.client.loadbalancer.reactive.LoadBalancerBeanPostProcessorAutoConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-12-28 16:59:51.958 [main] INFO - Bean 'org.springframework.cloud.client.loadbalancer.reactive.LoadBalancerBeanPostProcessorAutoConfiguration$ReactorDeferringLoadBalancerFilterConfig' of type [org.springframework.cloud.client.loadbalancer.reactive.LoadBalancerBeanPostProcessorAutoConfiguration$ReactorDeferringLoadBalancerFilterConfig] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-12-28 16:59:51.961 [main] INFO - Bean 'reactorDeferringLoadBalancerExchangeFilterFunction' of type [org.springframework.cloud.client.loadbalancer.reactive.DeferringLoadBalancerExchangeFilterFunction] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2023-12-28 16:59:55.286 [main] INFO - Loaded RoutePredicateFactory [After]
2023-12-28 16:59:55.286 [main] INFO - Loaded RoutePredicateFactory [Before]
2023-12-28 16:59:55.286 [main] INFO - Loaded RoutePredicateFactory [Between]
2023-12-28 16:59:55.286 [main] INFO - Loaded RoutePredicateFactory [Cookie]
2023-12-28 16:59:55.287 [main] INFO - Loaded RoutePredicateFactory [Header]
2023-12-28 16:59:55.287 [main] INFO - Loaded RoutePredicateFactory [Host]
2023-12-28 16:59:55.287 [main] INFO - Loaded RoutePredicateFactory [Method]
2023-12-28 16:59:55.287 [main] INFO - Loaded RoutePredicateFactory [Path]
2023-12-28 16:59:55.287 [main] INFO - Loaded RoutePredicateFactory [Query]
2023-12-28 16:59:55.287 [main] INFO - Loaded RoutePredicateFactory [ReadBody]
2023-12-28 16:59:55.287 [main] INFO - Loaded RoutePredicateFactory [RemoteAddr]
2023-12-28 16:59:55.287 [main] INFO - Loaded RoutePredicateFactory [XForwardedRemoteAddr]
2023-12-28 16:59:55.287 [main] INFO - Loaded RoutePredicateFactory [Weight]
2023-12-28 16:59:55.288 [main] INFO - Loaded RoutePredicateFactory [CloudFoundryRouteService]
2023-12-28 16:59:55.529 [main] INFO - For 'project-user' URL not provided. Will try picking an instance via load-balancing.
2023-12-28 16:59:56.183 [main] INFO -
Using generated security password: e0f0b5f2-a83b-47cc-a8d3-7cfd1cffc168
2023-12-28 17:00:00.214 [main] INFO - Netty started on port 30010
2023-12-28 17:00:01.320 [main] INFO - [ClientAuthPluginManager] Load ClientAuthService com.alibaba.nacos.client.auth.impl.NacosClientAuthServiceImpl success.
2023-12-28 17:00:01.320 [main] INFO - [ClientAuthPluginManager] Load ClientAuthService com.alibaba.nacos.client.auth.ram.RamClientAuthServiceImpl success.
2023-12-28 17:00:01.488 [main] INFO - nacos registry, project project-gateway 192.168.10.167:30010 register finished
2023-12-28 17:00:01.529 [main] INFO - Started Application in 18.751 seconds (JVM running for 23.371)
2023-12-28 17:00:01.556 [main] INFO - [Nacos Config] Listening config: dataId=project-gateway.yaml, group=project
2023-12-28 17:00:01.571 [main] INFO - [Nacos Config] Listening config: dataId=redis-config.yaml, group=project
logs/project-gateway/warn/project-gateway.warn.log 0 → 100644
2023-12-28 16:59:59.453 [main] WARN - Spring Cloud LoadBalancer is currently working with the default cache. While this cache implementation is useful for development and tests, it's recommended to use Caffeine cache in production.You can switch to using Caffeine cache, by adding it and org.springframework.cache.caffeine.CaffeineCacheManager to the classpath.
logs/project-order/error/project-order.error.log 0 → 100644
This diff could not be displayed because it is too large.
logs/project-order/info/project-order.info.log 0 → 100644
2023-12-27 01:00:00.011 [scheduling-1] INFO - 开始初始化，所有工程师的容量将根据日历表的记录进行计算设置
2023-12-27 01:01:38.436 [scheduling-1] INFO - 工作队/各级机构容量定时计算，根据相关的工程师的容量进行汇总
2023-12-27 01:30:00.004 [scheduling-1] INFO - 开始初始化，所有工程师的容量将根据日历表的记录进行计算设置
2023-12-27 02:00:00.002 [scheduling-1] INFO - 开始初始化，所有工程师的容量将根据日历表的记录进行计算设置
2023-12-27 02:01:38.013 [scheduling-1] INFO - 工作队/各级机构容量定时计算，根据相关的工程师的容量进行汇总
2023-12-27 02:30:00.013 [scheduling-1] INFO - 开始初始化，所有工程师的容量将根据日历表的记录进行计算设置
2023-12-27 03:00:00.015 [scheduling-1] INFO - 工作队/各级机构容量定时计算，根据相关的工程师的容量进行汇总
2023-12-27 03:00:00.017 [scheduling-1] INFO - 开始初始化，所有工程师的容量将根据日历表的记录进行计算设置
2023-12-27 03:30:00.014 [scheduling-1] INFO - 开始初始化，所有工程师的容量将根据日历表的记录进行计算设置
2023-12-27 04:00:00.001 [scheduling-1] INFO - 工作队/各级机构容量定时计算，根据相关的工程师的容量进行汇总
2023-12-27 04:00:00.004 [scheduling-1] INFO - 开始初始化，所有工程师的容量将根据日历表的记录进行计算设置
2023-12-27 04:30:00.005 [scheduling-1] INFO - 开始初始化，所有工程师的容量将根据日历表的记录进行计算设置
2023-12-27 05:00:00.004 [scheduling-1] INFO - 工作队/各级机构容量定时计算，根据相关的工程师的容量进行汇总
2023-12-27 05:00:00.032 [scheduling-1] INFO - 开始初始化，所有工程师的容量将根据日历表的记录进行计算设置
2023-12-27 05:30:00.014 [scheduling-1] INFO - 开始初始化，所有工程师的容量将根据日历表的记录进行计算设置
2023-12-27 06:00:00.011 [scheduling-1] INFO - 开始初始化，所有工程师的容量将根据日历表的记录进行计算设置
2023-12-27 06:01:38.308 [scheduling-1] INFO - 工作队/各级机构容量定时计算，根据相关的工程师的容量进行汇总
2023-12-27 06:30:00.009 [scheduling-1] INFO - 开始初始化，所有工程师的容量将根据日历表的记录进行计算设置
2023-12-27 07:00:00.009 [scheduling-1] INFO - 开始初始化，所有工程师的容量将根据日历表的记录进行计算设置
2023-12-27 07:01:38.004 [scheduling-1] INFO - 工作队/各级机构容量定时计算，根据相关的工程师的容量进行汇总
2023-12-27 07:30:00.003 [scheduling-1] INFO - 开始初始化，所有工程师的容量将根据日历表的记录进行计算设置
2023-12-27 08:00:00.008 [scheduling-1] INFO - 工作队/各级机构容量定时计算，根据相关的工程师的容量进行汇总
2023-12-27 08:00:00.010 [scheduling-1] INFO - 开始初始化，所有工程师的容量将根据日历表的记录进行计算设置
2023-12-27 08:30:00.008 [scheduling-1] INFO - 开始初始化，所有工程师的容量将根据日历表的记录进行计算设置
2023-12-27 09:00:00.007 [scheduling-1] INFO - 开始初始化，所有工程师的容量将根据日历表的记录进行计算设置
2023-12-27 09:01:47.011 [scheduling-1] INFO - 工作队/各级机构容量定时计算，根据相关的工程师的容量进行汇总
2023-12-27 09:30:00.011 [scheduling-1] INFO - 开始初始化，所有工程师的容量将根据日历表的记录进行计算设置
2023-12-27 10:00:00.010 [scheduling-1] INFO - 开始初始化，所有工程师的容量将根据日历表的记录进行计算设置
2023-12-27 10:02:14.365 [scheduling-1] INFO - 工作队/各级机构容量定时计算，根据相关的工程师的容量进行汇总
2023-12-27 10:30:00.019 [scheduling-1] INFO - 开始初始化，所有工程师的容量将根据日历表的记录进行计算设置
2023-12-27 11:00:00.013 [scheduling-1] INFO - 工作队/各级机构容量定时计算，根据相关的工程师的容量进行汇总
2023-12-27 11:00:00.016 [scheduling-1] INFO - 开始初始化，所有工程师的容量将根据日历表的记录进行计算设置
2023-12-27 11:30:00.007 [scheduling-1] INFO - 开始初始化，所有工程师的容量将根据日历表的记录进行计算设置
2023-12-27 11:35:00.006 [scheduling-1] INFO - >>> 服务类消息预警开始
2023-12-27 11:35:00.159 [scheduling-1] INFO - >>> 服务类消息预警结束
2023-12-27 12:00:00.005 [scheduling-1] INFO - 开始初始化，所有工程师的容量将根据日历表的记录进行计算设置
2023-12-27 12:01:44.164 [scheduling-1] INFO - 工作队/各级机构容量定时计算，根据相关的工程师的容量进行汇总
2023-12-27 12:30:00.013 [scheduling-1] INFO - 开始初始化，所有工程师的容量将根据日历表的记录进行计算设置
2023-12-27 13:00:00.016 [scheduling-1] INFO - 开始初始化，所有工程师的容量将根据日历表的记录进行计算设置
2023-12-27 13:01:46.369 [scheduling-1] INFO - 工作队/各级机构容量定时计算，根据相关的工程师的容量进行汇总
2023-12-27 13:30:00.015 [scheduling-1] INFO - 开始初始化，所有工程师的容量将根据日历表的记录进行计算设置
2023-12-27 14:00:00.016 [scheduling-1] INFO - 开始初始化，所有工程师的容量将根据日历表的记录进行计算设置
2023-12-27 14:01:55.598 [scheduling-1] INFO - 工作队/各级机构容量定时计算，根据相关的工程师的容量进行汇总
2023-12-27 14:30:00.013 [scheduling-1] INFO - 开始初始化，所有工程师的容量将根据日历表的记录进行计算设置
2023-12-27 15:00:00.015 [scheduling-1] INFO - 开始初始化，所有工程师的容量将根据日历表的记录进行计算设置
2023-12-27 15:02:01.582 [scheduling-1] INFO - 工作队/各级机构容量定时计算，根据相关的工程师的容量进行汇总
2023-12-27 15:30:00.052 [scheduling-1] INFO - 开始初始化，所有工程师的容量将根据日历表的记录进行计算设置
2023-12-27 15:35:00.363 [scheduling-1] INFO - >>> 服务类消息预警开始
2023-12-27 15:35:01.567 [scheduling-1] INFO - >>> 服务类消息预警结束
2023-12-27 16:00:00.314 [scheduling-1] INFO - 开始初始化，所有工程师的容量将根据日历表的记录进行计算设置
2023-12-27 16:03:54.151 [scheduling-1] INFO - 工作队/各级机构容量定时计算，根据相关的工程师的容量进行汇总
logs/project-order/warn/project-order.warn.log 0 → 100644
This diff could not be displayed because it is too large.
project-order/src/main/resources/static/doc/highlight.min.js 0 → 100644
This diff could not be displayed because it is too large.
project-order/src/main/resources/static/doc/index.html 0 → 100644
This diff could not be displayed because it is too large.
Markdown is supported
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!