2026-07-09 15:05:05.556 INFO 4632 — [ main] com.alibaba.nacos.common.remote.client : [RpcClientFactory] create a new rpc client of 4ba48cfa-0980-49c4-8412-eeffb9d5c26b_config-02026-07-09 15:05:05.596 INFO 4632 — [ main] org.reflections.Reflections : Reflections took 25 ms to scan 1 urls, producing 3 keys and 6 values2026-07-09 15:05:05.621 INFO 4632 — [ main] org.reflections.Reflections : Reflections took 12 ms to scan 1 urls, producing 4 keys and 9 values2026-07-09 15:05:05.633 INFO 4632 — [ main] org.reflections.Reflections : Reflections took 10 ms to scan 1 urls, producing 3 keys and 10 values2026-07-09 15:05:05.728 INFO 4632 — [ main] org.reflections.Reflections : Reflections took 93 ms to scan 145 urls, producing 0 keys and 0 values2026-07-09 15:05:05.737 INFO 4632 — [ main] org.reflections.Reflections : Reflections took 9 ms to scan 1 urls, producing 1 keys and 5 values2026-07-09 15:05:05.749 INFO 4632 — [ main] org.reflections.Reflections : Reflections took 10 ms to scan 1 urls, producing 1 keys and 7 values2026-07-09 15:05:05.760 INFO 4632 — [ main] org.reflections.Reflections : Reflections took 8 ms to scan 1 urls, producing 2 keys and 8 values2026-07-09 15:05:05.847 INFO 4632 — [ main] org.reflections.Reflections : Reflections took 86 ms to scan 145 urls, producing 0 keys and 0 values2026-07-09 15:05:05.849 INFO 4632 — [ main] com.alibaba.nacos.common.remote.client : [4ba48cfa-0980-49c4-8412-eeffb9d5c26b_config-0] RpcClient init label, labels {moduleconfig, Vipserver-Tagnull, sourcesdk, Amory-Tagnull, Location-Tagnull, taskId0, AppNameunknown}2026-07-09 15:05:05.850 INFO 4632 — [ main] com.alibaba.nacos.common.remote.client : [4ba48cfa-0980-49c4-8412-eeffb9d5c26b_config-0] Register server push request handler:com.alibaba.nacos.client.config.impl.ClientWorkerC o n f i g R p c T r a n s p o r t C l i e n t ConfigRpcTransportClientConfigRpcTransportClient$Lambda325 / 15445627782026 − 07 − 0915 : 05 : 05.850 I N F O 4632 − − − [ m a i n ] c o m . a l i b a b a . n a c o s . c o m m o n . r e m o t e . c l i e n t : [ 4 b a 48 c f a − 0980 − 49 c 4 − 8412 − e e f f b 9 d 5 c 26 b c o n f i g − 0 ] R e g i s t e r s e r v e r p u s h r e q u e s t h a n d l e r : c o m . a l i b a b a . n a c o s . c l i e n t . c o n f i g . i m p l . C l i e n t W o r k e r 325/1544562778 2026-07-09 15:05:05.850 INFO 4632 --- [ main] com.alibaba.nacos.common.remote.client : [4ba48cfa-0980-49c4-8412-eeffb9d5c26b_config-0] Register server push request handler:com.alibaba.nacos.client.config.impl.ClientWorker325/15445627782026−07−0915:05:05.850INFO4632−−−[main]com.alibaba.nacos.common.remote.client:[4ba48cfa−0980−49c4−8412−eeffb9d5c26bc​onfig−0]Registerserverpushrequesthandler:com.alibaba.nacos.client.config.impl.ClientWorkerConfigRpcTransportClientKaTeX parse error: Cant use function $ in math mode at position 7: Lambda$̲326/1801878707 …LambdaKaTeX parse error: Expected EOF, got at position 193: …d[common.yaml] ̲ group[DEFAULT_…ConnectResetRequestHandler2026-07-09 15:05:09.161 INFO 4632 — [t.remote.worker] com.alibaba.nacos.common.remote.client : [7a25d587-1d88-4071-868d-704c8c7a58f0] Notify connected event to listeners.2026-07-09 15:05:09.161 INFO 4632 — [ main] com.alibaba.nacos.common.remote.client : [7a25d587-1d88-4071-868d-704c8c7a58f0] Register server push request handler:com.alibaba.nacos.common.remote.client.RpcClient$$LambdaKaTeX parse error: Expected }, got EOF at end of input: …, replacement/{remaining}} to RewritePath2026-07-09 15:05:09.627 DEBUG 4632 — [oundedElastic-2] o.s.c.g.r.RouteDefinitionRouteLocator : RouteDefinition ReactiveCompositeDiscoveryClient_gateway-service applying filter {regexp/gateway-service/?(?.*), replacement/KaTeX parse error: Expected EOF, got } at position 12: {remaining}}̲ to RewritePath…{remaining}} to RewritePath2026-07-09 15:05:39.271 DEBUG 4632 — [oundedElastic-3] o.s.c.g.r.RouteDefinitionRouteLocator : RouteDefinition matched: ReactiveCompositeDiscoveryClient_gateway-service2026-07-09 15:05:39.271 DEBUG 4632 — [oundedElastic-3] o.s.c.g.r.RouteDefinitionRouteLocator : RouteDefinition app-service applying {_genkey_0/app-service/**} to Path2026-07-09 15:05:39.272 DEBUG 4632 — [oundedElastic-3] o.s.c.g.r.RouteDefinitionRouteLocator : RouteDefinition app-service applying filter {_genkey_01} to StripPrefix2026-07-09 15:05:39.272 DEBUG 4632 — [oundedElastic-3] o.s.c.g.r.RouteDefinitionRouteLocator : RouteDefinition matched: app-service这是一份 Spring Cloud Gateway 微服务网关 的启动日志完整记录了应用从初始化到成功注册至 Nacos 并开始提供路由服务的全过程。下面按阶段拆解关键信息1️⃣ Nacos 客户端初始化与连接 (Config Naming)Config 客户端 (用于配置中心)创建了 RPC 客户端 4ba48cfa-0980-49c4-8412-eeffb9d5c26b_config-0并成功连接到本地的 Nacos Server (127.0.0.1:8848)。Naming 客户端 (用于服务注册与发现)创建了另一个 RPC 客户端 7a25d587-1d88-4071-868d-704c8c7a58f0同样成功连接到 Nacos。这两个客户端分别负责从 Nacos 拉取配置和进行服务注册/发现是微服务架构的基础。2️⃣ Reflections 扫描org.reflections.Reflections 输出了一系列扫描日志耗时均在毫秒级用于扫描类路径上的注解和元数据。这是某些框架如 Sentinel、Spring Data内部的自检正常情况不影响启动。3️⃣ Nacos 配置加载与激活 ProfileNacos 配置中心尝试拉取多个 Data IDcommon.yaml、gateway-service、gateway-service.yaml、gateway-service-dev.yaml。其中前三个出现 WARN Ignore the empty nacos configuration表示这些配置项在 Nacos 中不存在或内容为空并非错误应用会忽略并继续加载存在的配置。最终成功加载了 gateway-service-dev.yaml、gateway-service.yaml、gateway-service、common.yaml 四个配置源。激活的 Profiledev来自 spring.profiles.active因此最终使用的是 gateway-service-dev.yaml 中的配置优先级最高。4️⃣ Spring Data Redis 扫描RepositoryConfigurationDelegate 提示进入了严格仓库模式并扫描了 Redis 仓库但发现 0 个 Redis Repository 接口。这说明项目引入了 spring-boot-starter-data-redis但并未定义自定义的 Redis Repository只是作为缓存或操作客户端使用不影响网关功能。5️⃣ Gateway 静态路由配置加载从 GatewayProperties 中加载了静态路由定义来自配置文件或代码textRouteDefinition{id‘app-service’, predicates[Path/app-service/**], filters[StripPrefix1], urilb://app-service}这条路由的含义匹配路径 /app-service/** 的请求去掉第一段路径前缀StripPrefix1转发到注册中心中的 app-service 服务lb:// 表示负载均衡。6️⃣ 加载 Gateway 内置的 PredicateFactory 和 FilterFactory日志列出了所有可用的路由断言工厂如 Path、Method、Header 等以及过滤器工厂这是 Gateway 启动时的常规初始化表明网关已准备好解析各类路由规则。7️⃣ Sentinel 集成流量控制text[Sentinel SpringCloudGateway] using AnonymousBlockRequestHandler, responseStatus: 429, responseBody: {“code”:429,“message”:“请求过于频繁请稍后再试”}[Sentinel SpringCloudGateway] register SentinelGatewayFilter with order: -2147483648[Sentinel SpringCloudGateway] register SentinelGatewayBlockExceptionHandlerSentinel 已自动配置采用默认的限流响应HTTP 429消息为“请求过于频繁请稍后再试”并注册了网关过滤器和异常处理器用于后续对路由进行流量控制。8️⃣ 动态路由加载服务发现在启动后期RouteDefinitionRouteLocator 从 服务发现 中加载了动态路由textRouteDefinition ReactiveCompositeDiscoveryClient_gateway-service applying {pattern/gateway-service/} to Path…filter {regexp/gateway-service/?(?.*), replacement/${remaining}} to RewritePath这意味着 Gateway 自动为注册到 Nacos 的服务 gateway-service 自身即本应用生成了一条动态路由路径为 /gateway-service/并剥离前缀后转发到本服务的根路径。这是一种自引用路由通常用于内部测试或调试。同时之前定义的静态路由 app-service 也被再次确认加载。9️⃣ Netty Web 服务器启动与端口绑定textNetty started on port 8080Gateway 基于 Spring WebFlux底层使用 Netty 作为嵌入式 Web 服务器成功监听 8080 端口准备接收外部请求。 Nacos 服务注册成功textnacos registry, DEFAULT_GROUP gateway-service 192.168.0.28:8080 register finished当前网关服务以 gateway-service 为服务名IP 192.168.0.28端口 8080成功注册到 Nacos 的 DEFAULT_GROUP 分组中可供其他服务发现和调用。1️⃣1️⃣ 应用启动完成textStarted GatewayApplication in 5.354 seconds (JVM running for 5.812)整个启动耗时约 5.3 秒应用已就绪。1️⃣2️⃣ 启动后 Nacos 动态监听与路由刷新Nacos 配置监听器启动监听上述四个 Data ID 的变更以实现配置热更新。之后反复打印 DEBUG 日志表示 RouteDefinitionRouteLocator 持续监控路由定义的变化并重新匹配路由。这是 Gateway 的正常运行时行为每当路由配置从 Nacos 或服务发现更新时都会重新计算路由映射。 总结当前网关提供的路由能力静态路由/app-service/** → 转发至 app-service负载均衡。动态服务发现路由/gateway-service/** → 转发至本服务根路径自引用。限流能力集成 Sentinel可针对任意路由配置流量控制规则。配置中心已与 Nacos 连接支持运行时动态调整路由、过滤器等配置。应用已正常启动准备接收外部 HTTP 请求。⚠️ 注意由于 allowCredentials(true) 和 addAllowedOriginPattern(“*”) 同时存在虽未在日志中直接体现但之前的 CORS 配置代码已给出在生产环境中建议收紧来源避免安全风险。