解决-----springCloud gateway 网关application.yml配置文件不生效导致无法路由 以及 不要添加devtools

最新推荐文章于 2024-09-27 22:55:13 发布
最新推荐文章于 2024-09-27 22:55:13 发布
阅读量1.7w 收藏 5
点赞数 2
分类专栏： springcloud
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/noDr_butTry/article/details/100050383
版权

说实话这个问题恶心死我了，特此记录一下

报错

com.alibaba.nacos.api.exception.NacosException: null
	at com.alibaba.nacos.api.config.ConfigFactory.createConfigService(ConfigFactory.java:45) ~[nacos-api-1.0.0.jar:na]
	at com.alibaba.nacos.api.NacosFactory.createConfigService(NacosFactory.java:41) ~[nacos-api-1.0.0.jar:na]
	at org.springframework.cloud.alibaba.nacos.NacosConfigProperties.configServiceInstance(NacosConfigProperties.java:343) ~[spring-cloud-alibaba-nacos-config-0.2.2.RELEASE.jar:0.2.2.RELEASE]
	at org.springframework.cloud.alibaba.nacos.NacosConfigAutoConfiguration.nacosContextRefresher(NacosConfigAutoConfiguration.java:63) [spring-cloud-alibaba-nacos-config-0.2.2.RELEASE.jar:0.2.2.RELEASE]
	at org.springframework.cloud.alibaba.nacos.NacosConfigAutoConfiguration$$EnhancerBySpringCGLIB$$dd92b3e6.CGLIB$nacosContextRefresher$2(<generated>) [spring-cloud-alibaba-nacos-config-0.2.2.RELEASE.jar:0.2.2.RELEASE]
	at org.springframework.cloud.alibaba.nacos.NacosConfigAutoConfiguration$$EnhancerBySpringCGLIB$$dd92b3e6$$FastClassBySpringCGLIB$$d405c6d7.invoke(<generated>) [spring-cloud-alibaba-nacos-config-0.2.2.RELEASE.jar:0.2.2.RELEASE]
	at org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:244) [spring-core-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:363) [spring-context-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at org.springframework.cloud.alibaba.nacos.NacosConfigAutoConfiguration$$EnhancerBySpringCGLIB$$dd92b3e6.nacosContextRefresher(<generated>) [spring-cloud-alibaba-nacos-config-0.2.2.RELEASE.jar:0.2.2.RELEASE]
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_202]
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[na:1.8.0_202]
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[na:1.8.0_202]
	at java.lang.reflect.Method.invoke(Method.java:498) ~[na:1.8.0_202]
	at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:154) [spring-beans-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at org.springframework.beans.factory.support.ConstructorResolver.instantiate(ConstructorResolver.java:622) [spring-beans-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at org.springframework.beans.factory.support.ConstructorResolver.instantiateUsingFactoryMethod(ConstructorResolver.java:607) [spring-beans-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateUsingFactoryMethod(AbstractAutowireCapableBeanFactory.java:1321) [spring-beans-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:1160) [spring-beans-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:555) [spring-beans-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:515) [spring-beans-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:320) [spring-beans-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222) ~[spring-beans-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:318) [spring-beans-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:199) [spring-beans-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:845) ~[spring-beans-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:877) ~[spring-context-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:549) ~[spring-context-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at org.springframework.boot.web.reactive.context.ReactiveWebServerApplicationContext.refresh(ReactiveWebServerApplicationContext.java:66) ~[spring-boot-2.1.6.RELEASE.jar:2.1.6.RELEASE]
	at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:742) ~[spring-boot-2.1.6.RELEASE.jar:2.1.6.RELEASE]
	at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:389) ~[spring-boot-2.1.6.RELEASE.jar:2.1.6.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:311) ~[spring-boot-2.1.6.RELEASE.jar:2.1.6.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1213) ~[spring-boot-2.1.6.RELEASE.jar:2.1.6.RELEASE]
	at org.springframework.boot.SpringApplication.run(SpringApplication.java:1202) ~[spring-boot-2.1.6.RELEASE.jar:2.1.6.RELEASE]
	at com.atguigu.gateway.GulimallGatewayApplication.main(GulimallGatewayApplication.java:19) ~[classes/:na]

2019-08-24 11:01:46.351  INFO 27048 --- [           main] o.s.s.c.ThreadPoolTaskScheduler          : Initializing ExecutorService
2019-08-24 11:01:46.483 ERROR 27048 --- [TaskScheduler-1] o.s.c.a.nacos.discovery.NacosWatch       : Error watching Nacos Service change

java.lang.IllegalArgumentException: no server available
	at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:354) ~[nacos-client-1.0.0.jar:na]
	at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:346) ~[nacos-client-1.0.0.jar:na]
	at com.alibaba.nacos.client.naming.net.NamingProxy.reqAPI(NamingProxy.java:294) ~[nacos-client-1.0.0.jar:na]
	at com.alibaba.nacos.client.naming.net.NamingProxy.getServiceList(NamingProxy.java:276) ~[nacos-client-1.0.0.jar:na]
	at com.alibaba.nacos.client.naming.net.NamingProxy.getServiceList(NamingProxy.java:252) ~[nacos-client-1.0.0.jar:na]
	at com.alibaba.nacos.client.naming.NacosNamingService.getServicesOfServer(NacosNamingService.java:525) ~[nacos-client-1.0.0.jar:na]
	at org.springframework.cloud.alibaba.nacos.discovery.NacosWatch.nacosServicesWatch(NacosWatch.java:127) ~[spring-cloud-alibaba-nacos-discovery-0.2.2.RELEASE.jar:0.2.2.RELEASE]
	at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54) ~[spring-context-5.1.8.RELEASE.jar:5.1.8.RELEASE]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[na:1.8.0_202]
	at java.util.concurrent.FutureTask.runAndReset$$$capture(FutureTask.java:308) ~[na:1.8.0_202]
	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java) ~[na:1.8.0_202]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) ~[na:1.8.0_202]
	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) ~[na:1.8.0_202]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[na:1.8.0_202]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[na:1.8.0_202]
	at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_202]

思考

1、查看了服务端口

在这里插入图片描述

查看端口结果是是默认的8080， 我的yml配置里是server.port=88, 我联想到yml配置文件没生效？

server:
  port: 88
 
spring:
  cloud:
    gateway:
      routes:
        - id: pms_route
          uri: lb://gulimall-pms
          predicates:
            - Path=/pms/**, /api/index/**, /api/item/**
          filters:
            # {} 是用来取值的
            - RewritePath=/api/(?<segment>.*), /$\{segment}

        - id: oms_route
          uri: lb://gulimall-oms
          predicates:
            - Path=/oms/**
            # filters:
            # - AddResponseHeader=heyijie,666
        - id: sms_route
          uri: lb://gulimall-sms
          predicates:
            - Path=/sms/**
        - id: ums_route
          uri: lb://gulimall-ums
          predicates:
            - Path=/ums/**, /api/ums/**
          filters:
            # {} 是用来取值的
            - RewritePath=/api/(?<segment>.*), /$\{segment}

        - id: wms_route
          uri: lb://gulimall-wms
          predicates:
            - Path=/wms/**
        - id: gulimall_search_route
          uri: lb://gulimall-search
          predicates:
            # 可能会有特殊字符转义 \{
            - Path=/api/search/**
          filters:
            - RewritePath=/api/(?<segment>.*), /$\{segment}

2、查看编译目录

如图，编译目录果然没有applicaiton.yml文件，springcloud gateway服务直接报错，路由也不生效

在这里插入图片描述

解决

3、修改application.yml重新编译 打包

编译目录下一定要有application.yml

查了一下可能是我application.yml的语法错了，修改了一下，重新编译打包后，编译目录下就有application.yml了，且该配置生效

建议不要添加devtools依赖

这个我也不太清除，加devtools的依赖，在有多个路由的时候，重启服务应用程序 application.yml文件时有时无的，建议还是不要加了, 如果有大佬能指点一二，就更好了

如果application.yml 不在编译目录下，那么访问网关的路由地址就会报错

{
    "timestamp": "2019-08-24T05:22:56.030+0000",
    "path": "/pms/skuinfo/cart/72",
    "status": 404,
    "error": "Not Found",
    "message": null,
	org.springframework.web.server.ResponseStatusException: 404 NOT_FOUND
		at org.springframework.web.reactive.resource.ResourceWebHandler.lambda$handle$0(ResourceWebHandler.java:325)
		at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:44)
		at reactor.core.publisher.MonoOnAssembly.subscribe(MonoOnAssembly.java:61)
		at reactor.core.publisher.Mono.subscribe(Mono.java:3848)
		at reactor.core.publisher.FluxSwitchIfEmpty$SwitchIfEmptySubscriber.onComplete(FluxSwitchIfEmpty.java:75)
		at reactor.core.publisher.FluxOnAssembly$OnAssemblySubscriber.onComplete(FluxOnAssembly.java:355)
		at reactor.core.publisher.MonoFlatMap$FlatMapMain.onComplete(MonoFlatMap.java:174)
		at reactor.core.publisher.FluxOnAssembly$OnAssemblySubscriber.onComplete(FluxOnAssembly.java:355)
		at reactor.core.publisher.MonoNext$NextSubscriber.onComplete(MonoNext.java:96)
		at reactor.core.publisher.FluxOnAssembly$OnAssemblySubscriber.onComplete(FluxOnAssembly.java:355)
		at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.drain(FluxConcatMap.java:360)
		at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.onSubscribe(FluxConcatMap.java:212)
		at reactor.core.publisher.FluxOnAssembly$OnAssemblySubscriber.onSubscribe(FluxOnAssembly.java:426)
		at reactor.core.publisher.FluxIterable.subscribe(FluxIterable.java:139)
		at reactor.core.publisher.FluxIterable.subscribe(FluxIterable.java:63)
		at reactor.core.publisher.FluxOnAssembly.subscribe(FluxOnAssembly.java:122)
		at reactor.core.publisher.FluxConcatMap.subscribe(FluxConcatMap.java:121)
		at reactor.core.publisher.FluxOnAssembly.subscribe(FluxOnAssembly.java:122)
		at reactor.core.publisher.MonoNext.subscribe(MonoNext.java:40)
		at reactor.core.publisher.MonoOnAssembly.subscribe(MonoOnAssembly.java:61)
		at reactor.core.publisher.MonoFlatMap.subscribe(MonoFlatMap.java:60)
		at reactor.core.publisher.MonoOnAssembly.subscribe(MonoOnAssembly.java:61)
		at reactor.core.publisher.MonoSwitchIfEmpty.subscribe(MonoSwitchIfEmpty.java:44)
		at reactor.core.publisher.MonoOnAssembly.subscribe(MonoOnAssembly.java:61)
		at reactor.core.publisher.MonoFlatMap.subscribe(MonoFlatMap.java:60)
		at reactor.core.publisher.MonoOnAssembly.subscribe(MonoOnAssembly.java:61)
		at reactor.core.publisher.Mono.subscribe(Mono.java:3848)
		at reactor.core.publisher.MonoIgnoreThen$ThenIgnoreMain.drain(MonoIgnoreThen.java:172)
		at reactor.core.publisher.MonoIgnoreThen.subscribe(MonoIgnoreThen.java:56)
		at reactor.core.publisher.MonoOnAssembly.subscribe(MonoOnAssembly.java:61)
		at reactor.core.publisher.MonoFlatMap$FlatMapMain.onNext(MonoFlatMap.java:150)
		at reactor.core.publisher.FluxOnAssembly$OnAssemblySubscriber.onNext(FluxOnAssembly.java:345)
		at reactor.core.publisher.FluxSwitchIfEmpty$SwitchIfEmptySubscriber.onNext(FluxSwitchIfEmpty.java:67)
		at reactor.core.publisher.FluxOnAssembly$OnAssemblySubscriber.onNext(FluxOnAssembly.java:345)
		at reactor.core.publisher.MonoNext$NextSubscriber.onNext(MonoNext.java:76)
		at reactor.core.publisher.FluxOnAssembly$OnAssemblySubscriber.onNext(FluxOnAssembly.java:345)
		at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.innerNext(FluxConcatMap.java:275)
		at reactor.core.publisher.FluxConcatMap$ConcatMapInner.onNext(FluxConcatMap.java:849)
		at reactor.core.publisher.FluxOnAssembly$OnAssemblySubscriber.onNext(FluxOnAssembly.java:345)
		at reactor.core.publisher.FluxMap$MapSubscriber.onNext(FluxMap.java:114)
		at reactor.core.publisher.FluxOnAssembly$OnAssemblySubscriber.onNext(FluxOnAssembly.java:345)
		at reactor.core.publisher.Operators$ScalarSubscription.request(Operators.java:2071)
		at reactor.core.publisher.FluxOnAssembly$OnAssemblySubscriber.request(FluxOnAssembly.java:442)
		at reactor.core.publisher.FluxMap$MapSubscriber.request(FluxMap.java:155)
		at reactor.core.publisher.FluxOnAssembly$OnAssemblySubscriber.request(FluxOnAssembly.java:442)
		at reactor.core.publisher.Operators$MultiSubscriptionSubscriber.set(Operators.java:1879)
		at reactor.core.publisher.Operators$MultiSubscriptionSubscriber.onSubscribe(Operators.java:1753)
		at reactor.core.publisher.FluxOnAssembly$OnAssemblySubscriber.onSubscribe(FluxOnAssembly.java:426)
		at reactor.core.publisher.FluxMap$MapSubscriber.onSubscribe(FluxMap.java:86)
		at reactor.core.publisher.FluxOnAssembly$OnAssemblySubscriber.onSubscribe(FluxOnAssembly.java:426)
		at reactor.core.publisher.MonoJust.subscribe(MonoJust.java:54)
		at reactor.core.publisher.MonoCallableOnAssembly.subscribe(MonoCallableOnAssembly.java:82)
		at reactor.core.publisher.MonoMap.subscribe(MonoMap.java:55)
		at reactor.core.publisher.MonoOnAssembly.subscribe(MonoOnAssembly.java:61)
		at reactor.core.publisher.Mono.subscribe(Mono.java:3848)
		at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.drain(FluxConcatMap.java:442)
		at reactor.core.publisher.FluxConcatMap$ConcatMapImmediate.onSubscribe(FluxConcatMap.java:212)
		at reactor.core.publisher.FluxOnAssembly$OnAssemblySubscriber.onSubscribe(FluxOnAssembly.java:426)
		at reactor.core.publisher.FluxIterable.subscribe(FluxIterable.java:139)
		at reactor.core.publisher.FluxIterable.subscribe(FluxIterable.java:63)
		at reactor.core.publisher.FluxOnAssembly.subscribe(FluxOnAssembly.java:122)
		at reactor.core.publisher.FluxConcatMap.subscribe(FluxConcatMap.java:121)
		at reactor.core.publisher.FluxOnAssembly.subscribe(FluxOnAssembly.java:122)
		at reactor.core.publisher.MonoNext.subscribe(MonoNext.java:40)
		at reactor.core.publisher.MonoOnAssembly.subscribe(MonoOnAssembly.java:61)
		at reactor.core.publisher.MonoSwitchIfEmpty.subscribe(MonoSwitchIfEmpty.java:44)
		at reactor.core.publisher.MonoOnAssembly.subscribe(MonoOnAssembly.java:61)
		at reactor.core.publisher.MonoFlatMap.subscribe(MonoFlatMap.java:60)
		at reactor.core.publisher.MonoOnAssembly.subscribe(MonoOnAssembly.java:61)
		at reactor.core.publisher.MonoFlatMap.subscribe(MonoFlatMap.java:60)
		at reactor.core.publisher.MonoOnAssembly.subscribe(MonoOnAssembly.java:61)
		at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:52)
		at reactor.core.publisher.MonoOnAssembly.subscribe(MonoOnAssembly.java:61)
		at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:52)
		at reactor.core.publisher.MonoOnAssembly.subscribe(MonoOnAssembly.java:61)
		at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:52)
		at reactor.core.publisher.MonoOnAssembly.subscribe(MonoOnAssembly.java:61)
		at reactor.core.publisher.MonoOnErrorResume.subscribe(MonoOnErrorResume.java:44)
		at reactor.core.publisher.MonoOnAssembly.subscribe(MonoOnAssembly.java:61)
		at reactor.core.publisher.MonoOnErrorResume.subscribe(MonoOnErrorResume.java:44)
		at reactor.core.publisher.MonoOnAssembly.subscribe(MonoOnAssembly.java:56)
		at reactor.core.publisher.MonoPeekTerminal.subscribe(MonoPeekTerminal.java:61)
		at reactor.core.publisher.MonoOnAssembly.subscribe(MonoOnAssembly.java:61)
		at reactor.core.publisher.MonoOnErrorResume.subscribe(MonoOnErrorResume.java:44)
		at reactor.core.publisher.MonoOnAssembly.subscribe(MonoOnAssembly.java:61)
		at reactor.core.publisher.Mono.subscribe(Mono.java:3848)
		at reactor.core.publisher.MonoIgnoreThen$ThenIgnoreMain.drain(MonoIgnoreThen.java:172)
		at reactor.core.publisher.MonoIgnoreThen.subscribe(MonoIgnoreThen.java:56)
		at reactor.core.publisher.MonoOnAssembly.subscribe(MonoOnAssembly.java:56)
		at reactor.core.publisher.MonoPeekFuseable.subscribe(MonoPeekFuseable.java:70)
		at reactor.core.publisher.MonoOnAssembly.subscribe(MonoOnAssembly.java:56)
		at reactor.core.publisher.MonoPeekTerminal.subscribe(MonoPeekTerminal.java:61)
		at reactor.core.publisher.MonoOnAssembly.subscribe(MonoOnAssembly.java:61)
		at reactor.netty.http.server.HttpServerHandle.onStateChange(HttpServerHandle.java:64)
		at reactor.netty.tcp.TcpServerBind$ChildObserver.onStateChange(TcpServerBind.java:226)
		at reactor.netty.http.server.HttpServerOperations.onInboundNext(HttpServerOperations.java:442)
		at reactor.netty.channel.ChannelOperationsHandler.channelRead(ChannelOperationsHandler.java:91)
		at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:374)
		at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:360)
		at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:352)
		at reactor.netty.http.server.HttpTrafficHandler.channelRead(HttpTrafficHandler.java:161)
		at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:374)
		at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:360)
		at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:352)
		at io.netty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandlerContext.fireChannelRead(CombinedChannelDuplexHandler.java:438)
		at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:323)
		at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:297)
		at io.netty.channel.CombinedChannelDuplexHandler.channelRead(CombinedChannelDuplexHandler.java:253)
		at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:374)
		at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:360)
		at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:352)
		at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1408)
		at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:374)
		at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:360)
		at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:930)
		at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:163)
		at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:682)
		at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:617)
		at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:534)
		at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:496)
		at io.netty.util.concurrent.SingleThreadEventExecutor$5.run(SingleThreadEventExecutor.java:906)
		at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
		at java.lang.Thread.run(Thread.java:748)
		Suppressed: reactor.core.publisher.FluxOnAssembly$OnAssemblyException: 
	Assembly trace from producer [reactor.core.publisher.MonoError] :
		reactor.core.publisher.Mono.error(Mono.java:261)
		org.springframework.web.reactive.resource.ResourceWebHandler.lambda$handle$0(ResourceWebHandler.java:325)
	Error has been observed by the following operator(s):
		|_	Mono.error ⇢  org.springframework.web.reactive.resource.ResourceWebHandler.lambda$handle$0(ResourceWebHandler.java:325)
		|_	Mono.defer ⇢ org.springframework.web.reactive.resource.ResourceWebHandler.handle(ResourceWebHandler.java:323)
		|_	Mono.switchIfEmpty ⇢ org.springframework.web.reactive.resource.ResourceWebHandler.handle(ResourceWebHandler.java:323)
		|_	Mono.flatMap ⇢ org.springframework.web.reactive.resource.ResourceWebHandler.handle(ResourceWebHandler.java:327)
		|_	Mono.then ⇢ org.springframework.web.reactive.result.SimpleHandlerAdapter.handle(SimpleHandlerAdapter.java:46)
		|_	Mono.flatMap ⇢ org.springframework.web.reactive.DispatcherHandler.handle(DispatcherHandler.java:151)
		|_	Mono.flatMap ⇢ org.springframework.web.reactive.DispatcherHandler.handle(DispatcherHandler.java:152)
		|_	Mono.defer ⇢ org.springframework.web.server.handler.DefaultWebFilterChain.filter(DefaultWebFilterChain.java:119)
		|_	Mono.defer ⇢ org.springframework.web.server.handler.DefaultWebFilterChain.filter(DefaultWebFilterChain.java:119)
		|_	Mono.defer ⇢ org.springframework.web.server.handler.DefaultWebFilterChain.filter(DefaultWebFilterChain.java:119)
noDr_butTry
关注
专栏目录
SpringCloud Gateway 配置过滤器不生效，我人麻了
m0_73311735的博客
10-12 9292
前段时间业务拓展搭建了一个新的微服务，然后要在网关配置路由，配置路由的时候配置了一个鉴权的过滤器，结果发现过滤器怎么都不生效，哇~~ 人都麻了。后来经过一通扒源码底裤，彻底搞清楚了原因，竟然是一个服务发现的配置导致的。和广大掘友一起分享~~百度不到问题的解决方案不重要，重要的是自己能掌握通过源码解决问题的能力。通过这次源码分析，让我一个从未花时间学习过组件的人几乎对它已经了如指掌~~~~
SpringCloud网关（gateway）配置
m0_74294530的博客
09-16 862
由于代码中使用json工具类解析nacos配置，故需要使用json格式填写配置内容。代表负载均衡，从注册中心获取目标微服务的实例列表，并且负载均衡选择一个访问。这里配合nacos注册中心使用。：路由断言，其实就是匹配条件。使用时需要将网关进行启动。
Springboot中yml文件不生效原因分析及解决
最新发布
技术萌新缓缓升级ing
09-27 528
本文分析了在Spring Boot项目中YML文件不生效的常见原因及解决方案。首先，YML文件的格式非常敏感，任何缩进或语法错误都可能导致配置无法解析，因此需确保格式正确。其次，文件命名和位置也至关重要，必须放在src/main/resources目录下，并命名为application.yml或application-{profile}.yml。此外，要检查是否激活了正确的Profile，并注意环境变量可能覆盖YML中的配置。代码中若有硬编码的配置也会导致YML失效。最后，确保所有依赖版本匹配，以避免因版本
SpringBoot中引入了springcloud-gateway，路由不生效为什么？
孤鹰的博客
03-17 1959
<plugin>
Spring Cloud Gateway网关整合
GMaya的博客
05-14 1077
介绍 Spring Cloud Gateway为Spring生态系统上的一个API网关组件，主要提供一种简单而有效的方式路由映射到指定的API，并为他们提供安全性、监控和限流等等。 创建项目 创建一个gmaya-gateway 项目。 修改pom文件 <!--gateway网关,内置webflux 依赖--> <dependency> <groupId>org.springframework.cloud</gro
SpringCloudGateway路由失效
小左的博客
02-02 8244
SpringCloudGateway 整合 nacos 路由失效的问题 报错如下 java.lang.IllegalStateException: Invalid host: lb://mall_admin_service 负载均衡配置的没有问题，对应的服务名称也没有问题，断点跟踪了一下，在这个RouteToRequestUrlFilter类中报错，代码很简单 if ("lb".equal...
IDEA中application.yml不生效
君莫笑
04-09 1万+
IDEA中application.yml不生效 可能是resources文件夹未被识别，可以在设置中使其生效！ 1、找到File下的Project Structure； 2、进入设置页面； 查看resources文件夹状态，若是和图中状态不一致则为未被识别的状态，此时application.yml不生效；选中resources文件夹再点击右上角Resources，设置成功。此时application.yml就生效了！ ...
spring cloud gateway 不生效
zhaozhangxiao2的博客
03-08 2210
自定义过滤器需要实现和Ordered。其中中的这个方法就是用来实现你的自定义的逻辑的示例：统计某个服务的响应时间。
SpringCloud第十章，升级篇，服务网关GateWay、服务配置Config和服务总线Bus
有一个小阿飞
04-24 2172
SpringCloud第十章，升级篇，服务网关GateWay、服务配置Config和服务总线Bus 一、服务网关GateWay 1、网关概述 为什么存在： 不同的微服务一般会有不同的网络地址，而外部的客户端可能需要调用多个微服务的接口才能完成一个业务的需求，如果让客 户端和多个微服务直接通信，会产生很多问题： a、客户端多次请求不同的微服务，增加客户端的复杂性 b、存在跨域请求，在一定场景下处理...
【springcloudAlibaba-Gateway（四）】
m0_71545814的博客
07-19 190
aa
【SpringCloud-5】gateway网关
growing_duck的博客
06-19 2079
GateWay
知识分享应用-后端代码从0构建
SwBack的博客
10-07 149
创建 Spring Boot 项目pom 在启动主类中，编写一个测试接口测试，成功提交：初始化项目新建 share-user 模块修改 share-user 模块的 pom.xml，添加之前父项目的依赖，并加入 lombok，加入 build 节点 修改父项目的 pom.xml，移除所有的依赖，移除 build，只保留依赖的版本管理 删除父项目的 srcapplication.ymlsrc 如图新建包，注意将启动主类放入 config 包启动，测试提交：新增 share-user 模块修改 UserApp
SpringCloud
惜听的博客
12-07 1559
一.总览 1.创建服务提供者和服务消费者，配置Nacos作为服务注册中心， 并把服务提供者和服务消费者用OpenFeign做远程调用。 2.配置Nacos作为服务配置中心。 3.配置GateWay网关。 4.整合Sentinel做服务降级。 二.Nacos作为注册中心的配置： 创建provider和consumer模块 1.两个模块中引入依赖 <dependencies> <!--基本的三个依赖--> <...
application.yml不生效，bootstrap.yml不生效的3种解决方案
热门推荐
qq_51239427的博客
03-06 2万+
application.yml和bootstrap.yml 是什么？ Spring Boot 默认支持properties(.properties) 和 YAML(.yml .yaml ) 两种格式的配置文件，yml 和 properties 文件都属于配置文件，功能一样。 一.加载顺序 1.若application.yml 和bootstrap.yml 在同一目录下：bootstrap.yml 先加载 application.yml后加载 2.属性覆盖问题 启动上下文时，Spring Clou.
application.yaml中配置没有生效问题解决
nobody_lo的博客
11-08 1万+
如果配置文件确认没有错误但是没有生效首先是要到编译目录去查看是否被编译过去了，如果没有，请先将项目clean在重启tomcat，切记 另外，yaml文件中的那些坑： （1）冒号:后面必须有空格，下级属性缩进一格（只支持空格不支持制表符tab） （2）保证不能有重复的一级节点。 （3）如果参数是以空格开始或结束的字符串，应使用单引号把他包进来。如果一个字符串参数包含特殊字符，也要用单引号包起来。 如...
application.yml不起作用
weixin_42961599的博客
08-13 303
启动idea HelloWorldapplication；tomcat仍然是8080。application.yml中指定了server port为8989。解决办法：pom.xml中删除pom。这样前段页面能正常显示了。在pom文件中误配置了。
SpringBoot 中 application.yml 文件不生效
cywleo的博客
03-28 5081
SpringBoot 中 application.yml 文件不生效——解决办法 经常出现修改了 application.yml 中的内容，运行项目的时候却不生效，点开运行后产生的 target 文件夹才发现里面并没有 application.yml ,说明 application.yml 没有被编译 解决方法： 在 pom.xml 文件的 resource 中配置一下 yml 文件，即添加上 <include>**/*.yml</include> 具体如下： <resour
spring cloud项目怎么确定引用application-dev.yml配置文件
05-31
在Spring Cloud项目中，可以通过`spring.profiles.active`属性来指定当前应用程序所处的环境。例如，将`spring.profiles.active`设置为`dev`，就表示当前应用程序处于开发环境。 在确定引用`application-dev.yml`配置文件时，可以通过以下方式来指定： 1. 在`bootstrap.yml`或`bootstrap.properties`配置文件中，可以通过`spring.cloud.config.name`和`spring.cloud.config.profile`属性来指定要加载的配置文件的名称和环境。例如，将`spring.cloud.config.name`设置为`application`，`spring.cloud.config.profile`设置为`dev`，就表示要加载`application-dev.yml`配置文件。 2. 在启动命令中，可以通过`--spring.profiles.active`选项来指定当前应用程序所处的环境。例如，使用以下命令启动应用程序： ``` java -jar myapp.jar --spring.profiles.active=dev ``` 就表示当前应用程序处于开发环境，会自动加载`application-dev.yml`配置文件。 无论使用哪种方式，Spring Cloud都会根据指定的配置文件名和环境来加载相应的配置文件。如果找不到指定的配置文件，则会抛出异常。
评论 1
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值