[I] go客户端设置了接口超时时间，在java 服务端无法获取到正确的值 [dubbo-go]

[via GitHub]

Jafeyyu opened a new issue, #2546:
URL: https://github.com/apache/dubbo-go/issues/2546

   ### Environment
   
   - Server: dubbo java 3.2.9
   - Client:  dubbo go 3.1.0
   - Protocol:  dubbo
   - Registry:  nacos
   
   ### Issue description
   go cliend调用java server的dubbo server，可以成功调用，但是go 
client接收到的时超时响应，设置了超时时间也无效，经调试，发现go 
client发送请求时，invocation的attachment里是设置了超时时间的，如下图
   
![1](https://github.com/apache/dubbo-go/assets/13826823/65f7d09a-9717-41ee-ab5b-41ceb847a3d6)
   但是java 
server端的org.apache.dubbo.rpc.filter.ProfilerServerFilter类中的dumpIfNeed方法中，从invocation的attachement获取timeout的值是0，如下图
   
![2](https://github.com/apache/dubbo-go/assets/13826823/f3046df6-59fc-41bb-8c3f-64262e2f1aa4)
   
   
   ### Logs
   
   <details><summary>Click me to check logs</summary>
   
   ```
   #服务端日志
   2023-12-26T10:16:44.780 
[DubboServerHandler-10.6.8.106:20880-thread-56] 16100 
 WARN o.a.d.r.filter.ProfilerServerFilter :  
[DUBBO] [Dubbo-Provider] execute service 
com.netpro.dubbo.dems.baseconfig.AlarmDubboService#add cost 160.479300 ms, this 
invocation almost (maybe already) timeout. Timeout: 0ms
   client: 10.6.8.106:1947
   invocation context:
   path=com.netpro.dubbo.dems.baseconfig.AlarmDubboService;
   async=false;
   input=764;
   environment=dev;
   dubbo=2.0.2;
   interface=com.netpro.dubbo.dems.baseconfig.AlarmDubboService;
   version=;
   timeout=0;
   thread info: 
   Start time: 1041345319061500
   +-[ Offset: 0.000000ms; Usage: 160.479300ms, 100% ] Receive request. Server 
invoke begin.
     +-[ Offset: 0.248700ms; Usage: 160.072500ms, 99% ] Receive request. Server 
biz impl invoke begin., dubbo version: 3.2.9, current host: 10.6.8.106, error 
code: 3-7. This may be caused by , go to https://dubbo.apache.org/faq/3/7 to 
find instructions. 
   
   
   
   #go客户端日志：
   2023-12-26 10:46:06  WARN    proxy/proxy.go:212      [CallProxy] received 
rpc err: Failed to invoke the method add in the service 
com.netpro.dubbo.dems.baseconfig.AlarmDubboService. Tried 1 times of the 
providers 
[dubbo://:@10.6.8.106:20880/?interface=com.netpro.dubbo.dems.baseconfig.AlarmDubboService&group=&version=
 
dubbo://:@10.6.8.106:20880/?interface=com.netpro.dubbo.dems.baseconfig.AlarmDubboService&group=&version=]
 (2/1)from the registry 
service-discovery-registry://10.5.0.15:8848?registry=nacos&registry.group=&registry.label=true&registry.namespace=dubboboot3&registry.preferred=false&registry.role=0&registry.timeout=5s&registry.ttl=15m&registry.weight=0&registry.zone=&remote-client-name=dubbo.registries-nacos-10.5.0.15%3A8848%2C10.5.0.16%3A8848%2C10.5.0.17%3A8848&simplified=false
 on the consumer 10.6.0.6 using the dubbo version 3.0.4. Last error is maybe 
the client read timeout or fail to decode tcp stream in Writer.Write.: maybe 
the client read timeout or fail to decode tcp stream 
 in Writer.Write
   
   ```
   
   </details>
   


-- 
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: notifications-unsubscr...@dubbo.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@dubbo.apache.org
For additional commands, e-mail: notifications-h...@dubbo.apache.org