SURYAS1306 commented on issue #15968: URL: https://github.com/apache/dubbo/issues/15968#issuecomment-3812699675
Went through the stack trace and the root cause seems to be a response codec mismatch, not a connectivity issue. The exception ultimately comes from a JSON parsing failure: Unrecognized token 'Hello' which suggests APISIX is returning plain text (ex: Hello null), while Dubbo’s Triple client is trying to decode the response as a Triple-encoded RPC response. The request does reach APISIX, but when the response is not in the expected Triple format, the client cancels the call. So this looks more like a protocol/codec compatibility problem between Dubbo Triple and APISIX, rather than a networking or registry issue. I’m digging further into where Triple response decoding happens and whether this should be addressed by: - adapting the Triple client or codec layer to handle this kind of response, or - introducing a dedicated codec or SPI extension for APISIX-style responses. - I’m willing to investigate deeper and try to propose a fix. -- 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]
