sheharyaar commented on issue #10648:
URL: https://github.com/apache/apisix/issues/10648#issuecomment-1887963429

   Your service is detected by dubbo-api when running with nacos : 
   
![image](https://github.com/apache/apisix/assets/34273345/92290303-3e77-443d-b203-6fde1d8e96fd)
   
   But the issue is that the method is not getting detected :
   
![image](https://github.com/apache/apisix/assets/34273345/bafff73a-cc26-4c93-b332-1ab06db74df7)
   
   There seems some issue with the application code. The output from APISIX is 
valid because APISIX expects `0x33` at the response body when it tries to 
decode it. But since the service is not detected and dubbo returns an error, 
the decoding fails. 
   ```
   2024-01-12 02:32:42.967 WARN  o.a.d.r.p.d.DecodeableRpcInvocation:83    
[DUBBO] Decode rpc invocation failed: Service not 
found:com.rrht.sys.service.impl.SysUserService:3.2.0, selectSysUserInfo, dubbo 
version: 2.7.8, current host: 192.168.0.108
   java.lang.IllegalArgumentException: Service not 
found:com.rrht.sys.service.impl.SysUserService:3.2.0, selectSysUserInfo
           at 
org.apache.dubbo.rpc.protocol.dubbo.DecodeableRpcInvocation.decode(DecodeableRpcInvocation.java:134)
           at 
org.apache.dubbo.rpc.protocol.dubbo.DecodeableRpcInvocation.decode(DecodeableRpcInvocation.java:80)
           at 
org.apache.dubbo.remoting.transport.DecodeHandler.decode(DecodeHandler.java:57)
           at 
org.apache.dubbo.remoting.transport.DecodeHandler.received(DecodeHandler.java:44)
           at 
org.apache.dubbo.remoting.transport.dispatcher.ChannelEventRunnable.run(ChannelEventRunnable.java:57)
           at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
           at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
           at java.lang.Thread.run(Thread.java:750)
    ```
   


-- 
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]

Reply via email to