Shulou(Shulou.com)06/03 Report--

This article focuses on "how to solve a large number of problems in the gateway gateway after upgrading boot". Interested friends may wish to have a look. The method introduced in this paper is simple, fast and practical. Let's let the editor take you to learn how to solve a large number of problems in the gateway gateway after upgrading boot.

Project version

Error 1:

Description:

An attempt was made to call a method that does not exist. The attempt was made from the following location:

Org.springframework.cloud.gateway.config.GatewayAutoConfiguration$NettyConfiguration.gatewayHttpClient (GatewayAutoConfiguration.java:612)

The following method did not exist:

Reactor.netty.resources.ConnectionProvider.elastic (Ljava/lang/String;Ljava/time/Duration;Ljava/time/Duration;) Lreactor/netty/resources/ConnectionProvider

The method's class, reactor.netty.resources.ConnectionProvider, is available from the following locations:

JarRlfileGetWord ("net"); "net"; "reactorlement", "reactorlement", "nettylage"0.9.1", "RELEASE", "net", "0.9.1" and "RELEASE.jarverse", "reactorlash"reactorlash"

It was loaded from the following location:

File:/E:/java/MAVEN/MavenRepo/io/projectreactor/netty/reactor-netty/0.9.1.RELEASE/reactor-netty-0.9.1.RELEASE.jar

The reason for this error is that although the corresponding cloud version of boot is H version after upgrading to 2.2.X, the netty of gateway version does not match. Therefore, the netty version needs to be introduced separately.

Solve

Error 2 Description:

An attempt was made to call a method that does not exist. The attempt was made from the following location:

Org.springframework.cloud.gateway.config.GatewayAutoConfiguration$NettyConfiguration.reactorNettyWebSocketClient (GatewayAutoConfiguration.java:738)

The following method did not exist:

Org.springframework.web.reactive.socket.client.ReactorNettyWebSocketClient.setHandlePing (Z) V

The method's class, org.springframework.web.reactive.socket.client.ReactorNettyWebSocketClient, is available from the following locations:

JarRepoxAccording to ReactorNettyWebSocketClient.class

It was loaded from the following location:

File:/E:/java/MAVEN/MavenRepo/org/springframework/spring-webflux/5.2.1.RELEASE/spring-webflux-5.2.1.RELEASE.jar

The reason for this error is the same. It is all due to version matching. The internal automatic configuration class cannot find the corresponding version dependency, so you need to introduce a separate version of spring-webflux. Be careful to introduce a higher version for backward compatibility, otherwise 5.2.1 will still generate errors.

Solve the problem of excluding webflux in the gateway gateway and introduce a new webflux because spring cloud gateway is based on webflux, and if you do not want web support, you need to import spring-boot-starter-webflux instead of spring-boot-start-web.

At this point, I believe you have a deeper understanding of "how to solve a large number of problems in the gateway gateway after upgrading boot". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.