On this page

Show all

Help Center/ Cloud Service Engine/ FAQs/ ServiceComb Engines/ Why Are Microservice Development Framework and Netty Versions Unmatched?

Why Are Microservice Development Framework and Netty Versions Unmatched?

Updated on 2023-11-08 GMT+08:00

View PDF

Symptom

During development of a microservice application, the following error is displayed:

"Caused by: java.lang.NoSuchMethodError: io.netty.handler.codec.http.websocketx.WebSocketClientHandshakerFactory.newHandshaker(Ljava/net/URI;Lio/netty/handler/codec/http/websocketx/WebSocketVersion;Ljava/lang/String;ZLio/netty/handler/codec/http/HttpHeaders;IZZJ)Lio/netty/handler/codec/http/websocketx/WebSocketClientHandshaker;"

Possible Cause

Third-party software introduced a mismatched version dependency.

Solution

Run the mvn dependency:tree command in the development environment to view the dependency tree and check whether the microservice development framework and Netty versions are matched.

For ServiceComb 2.0.1 development framework, the matched Netty version is 4.1.45.Final.

Parent topic: ServiceComb Engines

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot