forbetter100 opened a new issue, #10600: URL: https://github.com/apache/dubbo/issues/10600
<!-- If you need to report a security issue please visit https://github.com/apache/dubbo/security/policy --> I have searched the [issues](https://github.com/apache/dubbo/issues) of this repository and believe that this is not a duplicate. ## Ask your question here 根据官网的说法，Triple协议能完美兼容grpc协议，按照我的理解，应该属于"is a"的关系。 为了验证这个说法，我做了两个实验： 1. 将dubbo-samples里的“dubbo-samples-grpc”的经典“Greeter”作为Provider跑起来，Consumer用原生grpc来调用，这时候是能调通的。然后我发现，provider的声明里有这么一个细节，protocol=grpc，而不是tri。 > <dubbo:service interface="io.grpc.examples.helloworld.DubboGreeterGrpc$IGreeter" ref="greeterImpl" protocol="grpc"/> 2. 于是我做了第二个实验，我将这里的protocol改成tri > <dubbo:service interface="io.grpc.examples.helloworld.DubboGreeterGrpc$IGreeter" ref="greeterImpl" protocol="tri"/> 这时候，异常发生了，如下 `[10/09/22 11:50:01:001 CST] Dubbo-framework-shared-handler-thread-1 ERROR serial.SerializingExecutor: [DUBBO] Exception while executing runnable org.apache.dubbo.rpc.protocol.tri.stream.ServerStream$ServerTransportObserver$$Lambda$242/6102697@122e6b4, dubbo version: 3.0.7, current host: 192.168.1.20 java.lang.NullPointerException at org.apache.dubbo.rpc.protocol.tri.stream.ServerStream$ServerTransportObserver.doOnData(ServerStream.java:368) at org.apache.dubbo.rpc.protocol.tri.stream.ServerStream$ServerTransportObserver.lambda$onData$1(ServerStream.java:364) at org.apache.dubbo.rpc.protocol.tri.stream.ServerStream$ServerTransportObserver$$Lambda$242/6102697.run(Unknown Source) at org.apache.dubbo.common.threadpool.serial.SerializingExecutor.run(SerializingExecutor.java:99) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745)` 我是否可以理解，这本质是一种不兼容？以及，我的核心疑问，既然官网说triple完美兼容grpc，那么protocol=grpc的意义在哪里？ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
