[Bug][Java SDK (Component)] Functional bugs, which have affected usage

[wcy666103]

Pre-check

• I am sure that all the content I provide is in English.

Apache Dubbo Component

Java SDK (apache/dubbo)

Details

We will put functional errors, logical errors and other issues related to dubbo core links here, which will be solved as a priority

Code of Conduct

• I agree to follow this project's Code of Conduct

[wcy666103]

#14268 [Bug] The triple-rest-cors support added in version 3.3.0-beta.3 cannot be used.

Maybe he's the one responsible for the samples repository ci failure, which I found out happened after the pr merge here ref

#14236 [Bug] Example dubbo-samples-triple-rest-jaxrs runing failed in 3.3 #14236

#14293 [Bug] tri protocol does not work properly in dubbo 3.3.0-beta.4-snapshot version #14293

[wcy666103]

#14259 [Bug] 3.3.0-beta2 update to beta3, exception : module java.base does not "opens java.util" to unnamed module

hessian2 High jdk version adaptation

[wcy666103]

#14151 Triple default timeout is inconsistent with Dubbo

In TripleInvoker.java, the timeout behavior is inconsistent with DubboInvoker.java

[wcy666103]

#14126 [Bug] Using K8S as the registration center, the actual registration failed, but Dubbo will consider the registration successful

In the register method, the serviceInstance is initialized first before calling the doRegister method to actually register. Even if doRegister fails, the serviceInstance has already been initialized successfully. When the scheduled task reaches this point again, it will be considered successful and will not be registered again.

[wcy666103]

#14098 [Bug] Is there any graceful way to prevent running out of http2 stream id in Dubbo3.x

Based on the discussion in #13731, I think it is an improper way to make a reconnection triggered by GoAwayFrame(stream id exhausted) cause there will be 100% request failure before the new connection being active and it is unacceptable for production scenario. To make sure the connection is consistently available, is it possible to make a new connection before the stream id is about to be exhausted?

[wcy666103]

#14023 [Bug] The triple protocol is called through http, and the return value is incorrect #14023

Start the service using the TriPojoServer class of the dubco-samples-triple-no-IDl module and invoke the service using http,I understand that you should return “hello star“,but return "hello,{"request":"star"}"

[wcy666103]

#13666 [Context loss when async invoke](https://github.com/apache/dubbo/issues/13666#top) #13666

[wcy666103]

#13676 send flow control error when connection window is 0 #13676

[wcy666103]

#13578 native-image unit test inject reference bean failed #13578

NullPointerException, demoService is not inject, it is null

[wcy666103]

#13499 Warning stack when running with jdk 17, dubbo 3.3.0-beta.1, zookeeper, triple protocol #13499

I got a very long StackTrace as shown below. The process can still run properly though, so it's more like a warning stack.

[wcy666103]

#14254 Graceful closing does not work

after try, graceful shutdown works well at 3.1.5 and works well at 3.1.6, but not works at 3.2.11 and 3.2.13

[wcy666103]

#14347 When Service Discovery is enabled, the same registryId may create two ServiceDiscoveryRegistry

[wcy666103]

#14446 only support [jax-rs, spring-webmvc] annotation