Closed swift1911 closed 4 years ago
@swift1911 Is the serialization protocol used on the provider side hessian2?
@zyfjeff Yes , it should be hessian2. I have used the Dubbo default configuration. From Dubbo document, the default serialization protocol is hessian2. https://dubbo.apache.org/en-us/docs/user/references/protocol/dubbo.html
@swift1911 Can you post the results of the packet capture?
@zyfjeff I have uploaded my tcpdump result. dump.pcap.zip
It looks like an issue in dubbo-spring-boot-project.The version parameter of Reference is 0.0.0 https://github.com/apache/dubbo-spring-boot-project/issues/613
By the way, is it possible for Envoy to return or report the original error message of the Dubbo interface? The message "hessian type is not int 83" is not good for troubleshooting
This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or other activity occurs. Thank you for your contributions.
This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted". Thank you for your contributions.
Title: Envoy Dubbo Proxy Bad response: hessian type is not int 83
Version: Envoy 1.12.1 Dubbo 2.7.3(Both client and server)
Description: I have tested use Envoy as a front proxy for Dubbo Service, but i meet a problem.It seems related to the decoder.
Config:
Logs:
Dubbo Call Stack: