[gateway] springframework.core.io.buffer.DefaultDataBufferFactory cannot be cast to class org.spring

于 2023-04-27 11:35:25 发布
阅读量808 收藏
点赞数 2
文章标签： java 前端 spring
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/qq_42543063/article/details/130403020
版权

gateway jar包冲突导致的问题报错如下: 

java.lang.ClassCastException: class org.springframework.core.io.buffer.DefaultDataBufferFactory cannot be cast to class org.springframework.core.io.buffer.NettyDataBufferFactory (org.springframework.core.io.buffer.DefaultDataBufferFactory and org.springframework.core.io.buffer.NettyDataBufferFactory are in unnamed module of loader 'app')
	at org.springframework.cloud.gateway.filter.NettyWriteResponseFilter.lambda$filter$1(NettyWriteResponseFilter.java:82) ~[spring-cloud-gateway-core-2.2.1.RELEASE.jar:2.2.1.RELEASE]
	Suppressed: reactor.core.publisher.FluxOnAssembly$OnAssemblyException: 
Error has been observed at the following site(s):
	|_ checkpoint ⇢ org.springframework.web.cors.reactive.CorsWebFilter [DefaultWebFilterChain]
	|_ checkpoint ⇢ org.springframework.cloud.gateway.filter.WeightCalculatorWebFilter [DefaultWebFilterChain]
	|_ checkpoint ⇢ org.springframework.boot.actuate.metrics.web.reactive.server.MetricsWebFilter [DefaultWebFilterChain]
	|_ checkpoint ⇢ HTTP GET "/api/captcha.jpg?uuid=fb5f53c7-cbd3-429b-878e-55bf6e4c8bfd" [ExceptionHandlingWebHandler]
Stack trace:
		at org.springframework.cloud.gateway.filter.NettyWriteResponseFilter.lambda$filter$1(NettyWriteResponseFilter.java:82) ~[spring-cloud-gateway-core-2.2.1.RELEASE.jar:2.2.1.RELEASE]
		at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:44) ~[reactor-core-3.3.8.RELEASE.jar:3.3.8.RELEASE]
		at reactor.core.publisher.MonoIgnoreThen$ThenIgnoreMain.drain(MonoIgnoreThen.java:153) ~[reactor-core-3.3.8.RELEASE.jar:3.3.8.RELEASE]
		at reactor.core.publisher.MonoIgnoreThen$ThenIgnoreMain.ignoreDone(MonoIgnoreThen.java:190) ~[reactor-core-3.3.8.RELEASE.jar:3.3.8.RELEASE]
		at reactor.core.publisher.MonoIgnoreThen$ThenIgnoreInner.onComplete(MonoIgnoreThen.java:240) ~[reactor-core-3.3.8.RELEASE.jar:3.3.8.RELEASE]
		at reactor.core.publisher.MonoPeekTerminal$MonoTerminalPeekSubscriber.onComplete(MonoPeekTerminal.java:292) ~[reactor-core-3.3.8.RELEASE.jar:3.3.8.RELEASE]
		at reactor.core.publisher.MonoPeekTerminal$MonoTerminalPeekSubscriber.onComplete(MonoPeekTerminal.java:292) ~[reactor-core-3.3.8.RELEASE.jar:3.3.8.RELEASE]
		at reactor.core.publisher.Operators$MonoSubscriber.onComplete(Operators.java:1824) ~[reactor-core-3.3.8.RELEASE.jar:3.3.8.RELEASE]
		at reactor.core.publisher.MonoIgnoreThen$ThenAcceptInner.onComplete(MonoIgnoreThen.java:314) ~[reactor-core-3.3.8.RELEASE.jar:3.3.8.RELEASE]
		at reactor.core.publisher.Operators.complete(Operators.java:135) ~[reactor-core-3.3.8.RELEASE.jar:3.3.8.RELEASE]
		at reactor.core.publisher.MonoEmpty.subscribe(MonoEmpty.java:45) ~[reactor-core-3.3.8.RELEASE.jar:3.3.8.RELEASE]
		at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:52) ~[reactor-core-3.3.8.RELEASE.jar:3.3.8.RELEASE]
		at reactor.core.publisher.MonoDefer.subscribe(MonoDefer.java:52) ~[reactor-core-3.3.8.RELEASE.jar:3.3.8.RELEASE]
		at reactor.core.publisher.MonoIgnoreThen$ThenIgnoreMain.drain(MonoIgnoreThen.java:153) ~[reactor-core-3.3.8.RELEASE.jar:3.3.8.RELEASE]
		at reactor.core.publisher.MonoIgnoreThen$ThenIgnoreMain.ignoreDone(MonoIgnoreThen.java:190) ~[reactor-core-3.3.8.RELEASE.jar:3.3.8.RELEASE]
		at reactor.core.publisher.MonoIgnoreThen$ThenIgnoreInner.onComplete(MonoIgnoreThen.java:240) ~[reactor-core-3.3.8.RELEASE.jar:3.3.8.RELEASE]
		at reactor.core.publisher.Operators$ScalarSubscription.request(Operators.java:2346) ~[reactor-core-3.3.8.RELEASE.jar:3.3.8.RELEASE]
		at reactor.core.publisher.MonoFlatMapMany$FlatMapManyMain.onSubscribeInner(MonoFlatMapMany.java:143) ~[reactor-core-3.3.8.RELEASE.jar:3.3.8.RELEASE]
		at reactor.core.publisher.MonoFlatMapMany$FlatMapManyMain.onNext(MonoFlatMapMany.java:182) ~[reactor-core-3.3.8.RELEASE.jar:3.3.8.RELEASE]
		at reactor.core.publisher.SerializedSubscriber.onNext(SerializedSubscriber.java:99) ~[reactor-core-3.3.8.RELEASE.jar:3.3.8.RELEASE]
		at reactor.core.publisher.FluxRetryWhen$RetryWhenMainSubscriber.onNext(FluxRetryWhen.java:162) ~[reactor-core-3.3.8.RELEASE.jar:3.3.8.RELEASE]
		at reactor.core.publisher.MonoCreate$DefaultMonoSink.success(MonoCreate.java:156) ~[reactor-core-3.3.8.RELEASE.jar:3.3.8.RELEASE]
		at reactor.netty.http.client.HttpClientConnect$HttpIOHandlerObserver.onStateChange(HttpClientConnect.java:431) ~[reactor-netty-0.9.10.RELEASE.jar:0.9.10.RELEASE]
		at reactor.netty.ReactorNetty$CompositeConnectionObserver.onStateChange(ReactorNetty.java:514) ~[reactor-netty-0.9.10.RELEASE.jar:0.9.10.RELEASE]
		at reactor.netty.resources.PooledConnectionProvider$DisposableAcquire.onStateChange(PooledConnectionProvider.java:540) ~[reactor-netty-0.9.10.RELEASE.jar:0.9.10.RELEASE]
		at reactor.netty.resources.PooledConnectionProvider$PooledConnection.onStateChange(PooledConnectionProvider.java:427) ~[reactor-netty-0.9.10.RELEASE.jar:0.9.10.RELEASE]
		at reactor.netty.http.client.HttpClientOperations.onInboundNext(HttpClientOperations.java:574) ~[reactor-netty-0.9.10.RELEASE.jar:0.9.10.RELEASE]
		at reactor.netty.channel.ChannelOperationsHandler.channelRead(ChannelOperationsHandler.java:96) ~[reactor-netty-0.9.10.RELEASE.jar:0.9.10.RELEASE]
		at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) ~[netty-transport-4.1.51.Final.jar:4.1.51.Final]
		at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) ~[netty-transport-4.1.51.Final.jar:4.1.51.Final]
		at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357) ~[netty-transport-4.1.51.Final.jar:4.1.51.Final]
		at io.netty.channel.CombinedChannelDuplexHandler$DelegatingChannelHandlerContext.fireChannelRead(CombinedChannelDuplexHandler.java:436) ~[netty-transport-4.1.51.Final.jar:4.1.51.Final]
		at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:324) ~[netty-codec-4.1.51.Final.jar:4.1.51.Final]
		at io.netty.handler.codec.ByteToMessageDecoder.fireChannelRead(ByteToMessageDecoder.java:311) ~[netty-codec-4.1.51.Final.jar:4.1.51.Final]
		at io.netty.handler.codec.ByteToMessageDecoder.callDecode(ByteToMessageDecoder.java:425) ~[netty-codec-4.1.51.Final.jar:4.1.51.Final]
		at io.netty.handler.codec.ByteToMessageDecoder.channelRead(ByteToMessageDecoder.java:276) ~[netty-codec-4.1.51.Final.jar:4.1.51.Final]
		at io.netty.channel.CombinedChannelDuplexHandler.channelRead(CombinedChannelDuplexHandler.java:251) ~[netty-transport-4.1.51.Final.jar:4.1.51.Final]
		at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) ~[netty-transport-4.1.51.Final.jar:4.1.51.Final]
		at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) ~[netty-transport-4.1.51.Final.jar:4.1.51.Final]
		at io.netty.channel.AbstractChannelHandlerContext.fireChannelRead(AbstractChannelHandlerContext.java:357) ~[netty-transport-4.1.51.Final.jar:4.1.51.Final]
		at io.netty.channel.DefaultChannelPipeline$HeadContext.channelRead(DefaultChannelPipeline.java:1410) ~[netty-transport-4.1.51.Final.jar:4.1.51.Final]
		at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:379) ~[netty-transport-4.1.51.Final.jar:4.1.51.Final]
		at io.netty.channel.AbstractChannelHandlerContext.invokeChannelRead(AbstractChannelHandlerContext.java:365) ~[netty-transport-4.1.51.Final.jar:4.1.51.Final]
		at io.netty.channel.DefaultChannelPipeline.fireChannelRead(DefaultChannelPipeline.java:919) ~[netty-transport-4.1.51.Final.jar:4.1.51.Final]
		at io.netty.channel.nio.AbstractNioByteChannel$NioByteUnsafe.read(AbstractNioByteChannel.java:163) ~[netty-transport-4.1.51.Final.jar:4.1.51.Final]
		at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:714) ~[netty-transport-4.1.51.Final.jar:4.1.51.Final]
		at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:650) ~[netty-transport-4.1.51.Final.jar:4.1.51.Final]
		at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:576) ~[netty-transport-4.1.51.Final.jar:4.1.51.Final]
		at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493) ~[netty-transport-4.1.51.Final.jar:4.1.51.Final]
		at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989) ~[netty-common-4.1.51.Final.jar:4.1.51.Final]
		at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) ~[netty-common-4.1.51.Final.jar:4.1.51.Final]
		at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) ~[netty-common-4.1.51.Final.jar:4.1.51.Final]
		at java.base/java.lang.Thread.run(Thread.java:834) ~[na:na]

2023-04-27 11:27:43.103  INFO 26852 --- [erListUpdater-0] c.netflix.config.ChainedDynamicProperty  : Flipping property: renren-fast.ribbon.ActiveConnectionsLimit to use NEXT property: niws.loadbalancer.availabilityFilteringRule.activeConnectionsLimit = 2147483647

原因: gateway底层默认使用的是WebFlux , 而冲突包Tomcat所引入的是Netty,二者不兼容

解决办法: 在gateway项目pom依赖中使用<exclusion标签去除Tomcat-embed-core依赖。

        <dependency>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-starter-web</artifactId>
            <exclusions>
                <exclusion>
                    <groupId>org.springframework</groupId>
                    <artifactId>spring-webmvc</artifactId>
                </exclusion>
                <exclusion>
                    <groupId>org.apache.tomcat.embed</groupId>
                    <artifactId>tomcat-embed-core</artifactId>
                </exclusion>
            </exclusions>
        </dependency>

 

黄嚯嚯
关注
Gateway 报错org.springframework.core.io.buffer.DataBufferLimitException: Exceeded limit on max bytes..
For-的博客
04-30 4599
Spring Boot 版本：2.6.6 Spring Cloud Gateway 版本：3.1.1 由于在 Gateway 的自定义过滤器中重写了请求 ServerRequest，后面因为升级了架构，原本旧版本未对请求参数的大小进行限制（默认取-1），后面升级了新版修改为 256KB 的限制。 解决方案如下： 一、设置配置文件（失败） spring: codec: max-in-memory-size: 50MB 二、添加配置 Bean（失败） @Configuration @EnableW
【org.springframework.web.client.HttpServerErrorException$GatewayTimeout: 504 Gateway Time-out: [{“c】
libing666666的博客
06-25 1301
HttpServerErrorException$GatewayTimeout: 504 Gateway Time-out: [{"code":"30005", "message":"JTEOP: response timeout"}]
报java.lang.ClassCastException: org.springframework.core.io.buffer.DefaultDataBufferFactory cannot be
dzsflll的博客
04-24 2607
java.lang.ClassCastException: org.springframework.core.io.buffer.DefaultDataBufferFactory cannot be cast to org.springframework.core.io.buffer.NettyDataBufferFactory 导致原因是： 因为访问页面时候是通过servlet进行远程调用获取结...
org.springframework.core.io.buffer.DefaultDataBufferFactory cannot be cast to org.springframework.co
淮水竹亭
05-09 3068
  畅购商城使用gateway任务中，使用网址http://cloud.itheima.com:8001/brand请求无法解析，报如下错误： 报错信息：org.springframework.core.io.buffer.DefaultDataBufferFactory cannot be cast to org.springframework.core.io.buffer.NettyDataBufferFactory   首先确保自己的application.yml配置文件，host配置文件没有错误（
GateWay500异常：org.springframework.core.io.buffer.DefaultDataBufferFactory cannot be
qq_41473691的博客
09-13 1583
原因是：引入的依赖中有spring-web等依赖，排除或者删除掉这些依赖，gateway就能正常运行了！GateWay仅仅需要。可以看到通过网关访问成功!
DefaultDataBufferFactory cannot be cast to org.springframework.core.io.buffer.NettyDa
public__static的博客
12-10 606
这里写自定义目录标题新的改变功能快捷键合理的创建标题，有助于目录的生成如何改变文本的样式插入链接与图片如何插入一段漂亮的代码片生成一个适合你的列表创建一个表格设定内容居中、居左、居右SmartyPants创建一个自定义列表如何创建一个注脚注释也是必不可少的KaTeX数学公式新的甘特图功能，丰富你的文章UML 图表FLowchart流程图导出与导入导出导入 DefaultDataBufferFactory cannot be cast to org.springframework.core.io.buffer
.DefaultDataBufferFactory cannot be cast to org.springframework.core.io.buffer.NettyDataBufferFactor
y1639013776的博客
05-18 579
Spring Cloud GateWay异常处理：org.springframework.core.io.buffer.DefaultDataBufferFactory cannot be cast to org.springframework.core.io.buffer.NettyDataBufferFactory 深夜升级一个共同项目重启gateway突然报错，经过查了很多资料，最找找到了解决方法 idea全局搜索tomacat，注释掉gateway引用的tomcat依赖或者排除掉 ...
Observation$Context cannot be cast to class org.springframework.cloud.gateway.filter.headers.observation.GatewayContext
06-10
这个错误通常发生在使用Spring Cloud Gateway时，GatewayContext被错误地转换为ObservationContext的情况下。这可能是由于你的代码中有类型转换错误或者你的网关配置不正确导致的。 要解决这个问题，你需要检查你的...
springcloud 启动时报org.springframework.beans.factory.BeanCreationException注入 bean 失败异常。
weixin_55056055的博客
07-24 4355
springcloud 启动时就报bean注入异常。 /Library/Java/JavaVirtualMachines/jdk1.8.0_181.jdk/Contents/Home/bin/java -XX:TieredStopAtLevel=1 -noverify -Dspring.output.ansi.enabled=always -Dcom.sun.management.jmxremote -Dspring.jmx.enabled=true -Dspring.liveBeansView.mb.
springboot gateway 项目报org.springframework.http.codec.ServerCodecConfigurer
lazy_ting的博客
05-14 2196
Consider defining a bean of type 'org.springframework.http.codec.ServerCodecConfigurer' in your configuration.
DefaultDataBufferFactory can not be cast to
zhanghaisong_2015的博客
12-19 329
报错：java.lang.classCastException:org.springframework.core.io.buffer.DefaultDataBufferFactorycan not be cast to org.springframework.core.io.buffer.NettyDataBufferFactory 原因：spring网关是webflux 。不是tomcat 解决：排除servlet依赖 <exclusions> <exclusion&gt...
【SpringCloud】请求响应报错cannot be cast to org.springframework.core.io.buffer.NettyDataBufferFactory
开发学习工作日志
03-23 1815
springcloud gateway请求响应报错 org.springframework.core.io.buffer.DefaultDataBufferFactory cannot be cast to org.springframework.core.io.buffer.NettyDataBufferFactory 凡是下面这些和web, tomacat, servlet相关的依赖都不能带, 会与gateway中的webflux相冲突。 遇到的问题：gateway服务引入的依赖中包含了tomcat
DefaultDataBufferFactory cannot be cast to org.springframework.core.io.buffer.NettyDataBufferFactory
私は悪い人ですか的博客
01-31 4615
修改：在gateway中排除tomcat的依赖就可以 解释：gateway默认使用的是webFlux，而Tomcat使用的是netty
java.lang.ClassCastException: org.springframework.core.io.buffer.DefaultDataBufferFactory
Within的博客
08-24 1704
java.lang.ClassCastException: org.springframework.core.io.buffer.DefaultDataBufferFactory cannot be cast to org.springframework.core.io.buffer.NettyDataBufferFactory 导致原因是： 因为访问页面时候是通过servlet进行远程调用获取结果集的，而访问网关是用webflux直接接收的，但是当gateway网关微服务引入servelt时候，就会使
搭建SpringCloud父子分布式项目的gateway项目中遇到的坑 java.lang.ClassCastException: org.springframework.core.io.buffer
Alex Leon
10-31 685
搭建了一个父子分布式项目 但是配置gateway的时候, 由于各种依赖冲突导致gateway的路由无法生效 后来发现是因为父项目pom文件中引入的部分依赖和gateway依赖有冲突 总结: 下面这些依赖和springcloud gateway相冲突造成以下冲突 java.lang.ClassCastException: org.springframework.core.io.buffer.DefaultDataBufferFactory cannot be cast to org.springframewo
Spring Cloud GateWay异常处理：DefaultDataBuffer cannot be cast to org.springframework.core.io.b
JesusMak的博客
06-10 1340
Spring Cloud GateWay异常处理：DefaultDataBuffer cannot be cast to org.springframework.core.io.b 1. 问题描述： 使用spring cloud gateway组件时，按照官方文档配置后发现后台报错，并且配置不起作用 配置信息： 错误信息： 2. 解决办法： 网上资料说与SpringBoot中的spring-web-starter依赖冲突，但是在网关服务pom文件里没有添加spring-web-starter依赖。最后发现
【SpringGateway】java.lang.ClassCastException: org.springframework.core.io.buffer.DefaultDataBufferFac
THE1的博客
04-27 1097
解决方法：排除servlet 依赖 gateway：webflux底层为 netty [3f0264ef] There was an unexpected error (type=Internal Server Error, status=500). org.springframework.core.io.buffer.DefaultDataBufferFactory cannot be cast to org.springframework.core.io.buffer.NettyDataBufferFa
gateway异常：DefaultDataBuffer cannot be cast to org.springframework.core.io.buffer.NettyDataBuffer
热门推荐
sinat_37909570的博客
12-13 1万+
解决方法： 从依赖中删除 tomcat相关的依赖，我的删除下面就ok ` org.springframework.boot spring-boot-starter-tomcat
org.springframework.core.io.buffer.DataBufferLimitException: Exceeded limit on max bytes to buffer : 262144
最新发布
01-14
### 解决 Spring WebFlux 中 DataBufferLimitException 超出最大字节数限制 在 Spring WebFlux 框架中遇到 `DataBufferLimitException` 异常通常是因为请求体大小超过了默认的最大缓冲区限制。对于这个问题，可以通过调整应用程序中的配置来增加允许的最大字节数。 #### 配置 WebClient 请求体大小限制 为了防止客户端发送过大请求导致服务器资源耗尽，默认情况下设置了 262144 字节 (即 256 KB) 的上限。如果确实需要支持更大的请求，则可以在应用启动时通过自定义配置覆盖此默认值： ```yaml spring: codec: max-in-memory-size: 10MB # 设置为适合业务需求的大小 ``` 上述 YAML 文件片段展示了如何修改 application.yml 来增大内存中可以存储的数据量[^2]。 另外一种做法是在创建 WebClient 实例的时候指定编码器参数: ```java import org.springframework.http.codec.ClientCodecConfigurer; import reactor.netty.http.client.HttpClient; HttpClient httpClient = HttpClient.create() .option(ChannelOption.CONNECT_TIMEOUT_MILLIS, 5000) .responseTimeout(Duration.ofMillis(5000)) .doOnConnected(conn -> conn.addHandlerLast(new ReadTimeoutHandler(5)) .addHandlerLast(new WriteTimeoutHandler(5))); WebClient webClient = WebClient.builder() .clientConnector(new ReactorClientHttpConnector(httpClient)) .codecs(configurer -> configurer.defaultCodecs().maxInMemorySize(10 * 1024 * 1024)) // 单位是byte .build(); ``` 这段代码示例说明了怎样利用编程的方式设定 WebClient 的最大入站消息尺寸。 #### Gateway 层面的解决方案 如果是作为 API 网关使用的 Spring Cloud Gateway 抛出了同样的错误信息，那么还需要考虑网关本身的设置。同样地，可以通过 properties 或者 yaml 文件来进行全局性的更改： ```properties spring.cloud.gateway.globalcors.add-to-simple-url-handler-mapping=true spring.cloud.gateway.httpclient.max-in-memory-size=10MB ``` 以上属性适用于整个网关服务下的所有路由规则[^1]。 最后值得注意的是，在放宽这些限制的同时也要注意安全性考量，确保不会因为过度开放而引入潜在风险。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值