apache / dubbo

The java implementation of Apache Dubbo. An RPC and microservice framework.
https://dubbo.apache.org/
Apache License 2.0
40.54k stars 26.44k forks source link

[Bug] consumer invoke provider by http3 start fail #14885

Open zzps opened 2 weeks ago

zzps commented 2 weeks ago

Pre-check

Search before asking

Apache Dubbo Component

Java SDK (apache/dubbo)

Dubbo Version

dubbo 3.3.2 , openjdk17, windows11

Steps to reproduce this issue

refer to https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-triple-http3/README.md provider service config like that and use curl test, and it works http3 success. but use consumer invoke the provider by rpc use http3 the consumer start failed. follow is the image 1731304976386 both provider and consumer config as th image 1731305040854 consumer start failed with the error

What you expected to happen

consumer invoke provider by rpc use http3 success

Anything else

No response

Are you willing to submit a pull request to fix on your own?

Code of Conduct

oxsean commented 2 weeks ago

Could you please provider a demo?

zzps commented 2 weeks ago

Could you please provider a demo?

https://gitee.com/755157298/dubbo-tree.git

zzps commented 1 week ago

Could you please provider a demo? here is the demo,you can test [https://gitee.com/755157298/dubbo-tree.git](https://github.com/apache/dubbo/issues/url)

oxsean commented 1 week ago

Sorry, this is an http3 negotiation bug that needs to be fixed, you run your demo by modifying the configuration:

dubbo.protocol.triple.http3.negotiation=false

to turn off the http3 negotiation, after modified I can run your demo locally.

oxsean commented 1 week ago

Fixed in https://github.com/apache/dubbo/pull/14901

zzps commented 1 week ago

Sorry, this is an http3 negotiation bug that needs to be fixed, you run your demo by modifying the configuration:

dubbo.protocol.triple.http3.negotiation=false

to turn off the http3 negotiation, after modified I can run your demo locally.

so modify the word 'negotiate' to 'negotiation' ,then run ok?

zzps commented 1 week ago

Sorry, this is an http3 negotiation bug that needs to be fixed, you run your demo by modifying the configuration:

dubbo.protocol.triple.http3.negotiation=false

to turn off the http3 negotiation, after modified I can run your demo locally.

after i modify the configuration dubbo.protocol.triple.http3.negotiate=false to dubbo.protocol.triple.http3.negotiation=false and start success,alse i can see the http3 establish. but the consumer print a schedule error as below image 1731903235474

oxsean commented 1 week ago

Sorry, this is an http3 negotiation bug that needs to be fixed, you run your demo by modifying the configuration:

dubbo.protocol.triple.http3.negotiation=false

to turn off the http3 negotiation, after modified I can run your demo locally.

after i modify the configuration dubbo.protocol.triple.http3.negotiate=false to dubbo.protocol.triple.http3.negotiation=false and start success,alse i can see the http3 establish. but the consumer print a schedule error as below image 1731903235474

Check provider runing properly.

zzps commented 1 week ago

Sorry, this is an http3 negotiation bug that needs to be fixed, you run your demo by modifying the configuration:

dubbo.protocol.triple.http3.negotiation=false

to turn off the http3 negotiation, after modified I can run your demo locally.

after i modify the configuration dubbo.protocol.triple.http3.negotiate=false to dubbo.protocol.triple.http3.negotiation=false and start success,alse i can see the http3 establish. but the consumer print a schedule error as below image 1731903235474

Check provider runing properly.

the provider runing properly, the cunsumer runing properly first,and wait about 5 minutes.the consumer will print the error period

oxsean commented 1 week ago

Seem h3 Idle process has some problem, need further investigation.

zzps commented 6 days ago

Seem h3 Idle process has some problem, need further investigation. you can use up demo to see it ,just start and wait few minutes