You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@dubbo.apache.org by "vipyxc-byte (via GitHub)" <gi...@apache.org> on 2025/08/22 03:33:43 UTC

[I] [BUG] 客户端访问报session Already Closed 客户端消费者无法自动恢复 [dubbo-go]

vipyxc-byte opened a new issue, #2981:
URL: https://github.com/apache/dubbo-go/issues/2981

   ### ✅ Verification Checklist
   
   - [x] 🔍 I have searched the [existing issues](https://github.com/apache/dubbo-go/issues) and confirmed this is not a duplicate
   
   ### 🚀 Go Version
   
   1.23.3
   
   ### 📦 Dubbo-go Version
   
   v3.3.0
   
   ### 🖥️ Server Configuration
   
   _No response_
   
   ### 💻 Client Configuration
   
   _No response_
   
   ### 🌐 Protocol Configuration
   
   _No response_
   
   ### 📋 Registry Configuration
   
   _No response_
   
   ### 💾 Operating System
   
   🍎 macOS
   
   ### 📝 Bug Description
   
   closed:k8s 集群provider部署后,客户端访问报session Already Closed 客户端消费者无法自动恢复 #2739 
   #2739 没有相关的解决方案
   现象:
   1. Failed to invoke the method getDeviceInfo in the service xxxx. Tried 2 times of the providers [dubbo://:@10.202.244.89:40110/?interface=xxx&group=&version= dubbo://:@10.202.244.98:40110/?interface=xxx&group=&version= dubbo://:@10.202.244.98:40110/?interface=xxx&group=&version=] (3/2)from the registry zookeeper://10.202.244.31:2181?registry=zookeeper&registry.group=&registry.id=zk&registry.label=true&registry.namespace=&registry.preferred=false&registry.role=0&registry.timeout=10s&registry.ttl=20s&registry.weight=0&registry.zone=&remote-client-name=dubbo.registries-zookeeper-10.202.244.31%3A2181&simplified=false on the consumer 192.168.171.167 using the dubbo version 3.2.0. Last error is session Already Closed.
   2. dubbo-getty@v1.4.10/client.go:346打印日志,一直在连接旧的地址:net.DialTimeout(addr:10.202.244.98:40110, timeout:3e+09) = error:dial tcp 10.202.244.98:40110: connect: connection refused\ngithub.com/apache/dubbo-getty.(*client).dialTCP\n\t/root/go/pkg/mod/github.com/apache/dubbo-getty@v1.4.10/client.go:173\ngithub.com/apache/dubbo-getty.(*client).dial\n\t/root/go/pkg/mod/github.com/apache/dubbo-getty@v1.4.10/client.go:346\ngithub.com/apache/dubbo-getty.(*client).connect\n\t/root/go/pkg/mod/github.com/apache/dubbo-getty@v1.4.10/client.go:384\ngithub.com/apache/dubbo-getty.(*client).reConnect\n\t/root/go/pkg/mod/github.com/apache/dubbo-getty@v1.4.10/client.go:441\ngithub.com/apache/dubbo-getty.(*session).stop.func1\n\t/root/go/pkg/mod/github.com/apache/dubbo-getty@v1.4.10/session.go:863\nsync.(*Once).doSlow\n\t/usr/local/go/src/sync/once.go:78\nsync.(*Once).Do\n\t/usr/local/go/src/sync/once.go:69\ngithub.com/apache/dubbo-getty.(*session).stop\n\t/root/go/pkg/mod/git
 hub.com/apache/dubbo-getty@v1.4.10/session.go:853\ngithub.com/apache/dubbo-getty.(*session).handlePackage.func1\n\t/root/go/pkg/mod/github.com/apache/dubbo-getty@v1.4.10/session.go:595\ngithub.com/apache/dubbo-getty.(*session).handlePackage\n\t/root/go/pkg/mod/github.com/apache/dubbo-getty@v1.4.10/session.go:622\nruntime.goexit\n\t/usr/local/go/src/runtime/asm_amd64.s:1700
   
   ### 🔄 Steps to Reproduce
   
   1. 可能服务端频繁重启偶现此情况
   2. 当zk宕机一段时间后恢复出现此情况
   
   ### ✅ Expected Behavior
   
   自动恢复
   
   ### ❌ Actual Behavior
   
   无法自动恢复
   
   ### 💡 Possible Solution
   
   _No response_


-- 
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-unsubscribe@dubbo.apache.org.apache.org

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


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


Re: [I] [BUG] 泛化调用报session Already Closed 客户端无法自动恢复 [dubbo-go]

Posted by "Alanxtl (via GitHub)" <gi...@apache.org>.
Alanxtl commented on issue #2981:
URL: https://github.com/apache/dubbo-go/issues/2981#issuecomment-3485505111

   > 按照官方的泛化调用使用姿势也遇到这个问题,历史上好像有人也提过这个 [#2739](https://github.com/apache/dubbo-go/issues/2739) 在哪一个版本解决掉了呢?
   > 
   > session Already Closed github.com/apache/dubbo-getty.init :1 runtime.doInit1 /usr/local/go/src/runtime/proc.go:7353 runtime.doInit /usr/local/go/src/runtime/proc.go:7320 runtime.main /usr/local/go/src/runtime/proc.go:254 runtime.goexit /usr/local/go/src/runtime/asm_amd64.s:1700
   > 
   > xxx/xxx/xxx/ai/pkg/transporter/dubbo.Invoke /compile/src/pkg/transporter/dubbo/generic_invoke.go:68 tuya.com/xxx/xxx/ai/pkg/transporter/dubbo.InvokeAndDecoded[...] /compile/src/pkg/transporter/dubbo/generic_invoke.go:83 tuya.com/xxx/xxx/ai/pkg/transporter/dubbo.ProxyInvoke[...] /compile/src/pkg/transporter/dubbo/generic_invoke_proxy.go:77 tuya.com/xxx/xxx/ai/pkg/infra.(*jwtKeypairManager).getPublicKeyBySecretId /compile/src/pkg/infra/jwt_keypair.go:137 tuya.com/xxx/xxx/ai/pkg/infra.GetPublicKeyForJwt /compile/src/pkg/infra/jwt_keypair.go:88 tuya.com/xxx/xxx/ai/pkg/infra.VerifyTenantJwtToken /compile/src/pkg/infra/jwt_keypair.go:232 tuya.com/xxx/xxx/ai/pkg/proxy_mcp.initStreamableMcpServerM3.VerifyMiddleware.TokenVerify.func9 /compile/src/pkg/proxy_mcp/mcp_token_verify.go:41
   
   请问是哪个官方示例调用的时候是有问题的呢,我测试了dubbo-go-samples/compatibility/generic没出现这种情况


-- 
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-unsubscribe@dubbo.apache.org

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


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


Re: [I] [BUG] 泛化调用报session Already Closed 客户端无法自动恢复 [dubbo-go]

Posted by "vipyxc-byte (via GitHub)" <gi...@apache.org>.
vipyxc-byte commented on issue #2981:
URL: https://github.com/apache/dubbo-go/issues/2981#issuecomment-3509121095

   > > 按照官方的泛化调用使用姿势也遇到这个问题,历史上好像有人也提过这个 [#2739](https://github.com/apache/dubbo-go/issues/2739) 在哪一个版本解决掉了呢?
   > > session Already Closed github.com/apache/dubbo-getty.init :1 runtime.doInit1 /usr/local/go/src/runtime/proc.go:7353 runtime.doInit /usr/local/go/src/runtime/proc.go:7320 runtime.main /usr/local/go/src/runtime/proc.go:254 runtime.goexit /usr/local/go/src/runtime/asm_amd64.s:1700
   > > xxx/xxx/xxx/ai/pkg/transporter/dubbo.Invoke /compile/src/pkg/transporter/dubbo/generic_invoke.go:68 tuya.com/xxx/xxx/ai/pkg/transporter/dubbo.InvokeAndDecoded[...] /compile/src/pkg/transporter/dubbo/generic_invoke.go:83 tuya.com/xxx/xxx/ai/pkg/transporter/dubbo.ProxyInvoke[...] /compile/src/pkg/transporter/dubbo/generic_invoke_proxy.go:77 tuya.com/xxx/xxx/ai/pkg/infra.(*jwtKeypairManager).getPublicKeyBySecretId /compile/src/pkg/infra/jwt_keypair.go:137 tuya.com/xxx/xxx/ai/pkg/infra.GetPublicKeyForJwt /compile/src/pkg/infra/jwt_keypair.go:88 tuya.com/xxx/xxx/ai/pkg/infra.VerifyTenantJwtToken /compile/src/pkg/infra/jwt_keypair.go:232 tuya.com/xxx/xxx/ai/pkg/proxy_mcp.initStreamableMcpServerM3.VerifyMiddleware.TokenVerify.func9 /compile/src/pkg/proxy_mcp/mcp_token_verify.go:41
   > 
   > 请问是哪个官方示例调用的时候是有问题的呢,我测试了dubbo-go-samples/compatibility/generic没出现这种情况
   
   服务端频繁重启会导致这样的情况,我在本地测试没有模拟出,但是k8s频繁重启/发布会导致session Already Closed


-- 
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-unsubscribe@dubbo.apache.org

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


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


Re: [I] [BUG] 泛化调用报session Already Closed 客户端无法自动恢复 [dubbo-go]

Posted by "Alanxtl (via GitHub)" <gi...@apache.org>.
Alanxtl closed issue #2981: [BUG] 泛化调用报session Already Closed 客户端无法自动恢复
URL: https://github.com/apache/dubbo-go/issues/2981


-- 
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-unsubscribe@dubbo.apache.org

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


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


Re: [I] [BUG] 泛化调用报session Already Closed 客户端无法自动恢复 [dubbo-go]

Posted by "Alanxtl (via GitHub)" <gi...@apache.org>.
Alanxtl commented on issue #2981:
URL: https://github.com/apache/dubbo-go/issues/2981#issuecomment-3485675264

   > https://cn.dubbo.apache.org/zh-cn/overview/mannual/golang-sdk/refer/generic/ 早期(25年初)是基于这个文档实现的
   
   这个示例我们之前更新过,现在的位置在这里https://github.com/apache/dubbo-go-samples/tree/main/compatibility/generic 最新的版本我目前没有复现出问题,如果有复现代码可以贴上来,我们继续跟进 :)
   


-- 
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-unsubscribe@dubbo.apache.org

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


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


Re: [I] [BUG] 泛化调用报session Already Closed 客户端无法自动恢复 [dubbo-go]

Posted by "vipyxc-byte (via GitHub)" <gi...@apache.org>.
vipyxc-byte commented on issue #2981:
URL: https://github.com/apache/dubbo-go/issues/2981#issuecomment-3434938303

   > 按照官方的泛化调用使用姿势也遇到这个问题,历史上好像有人也提过这个 [#2739](https://github.com/apache/dubbo-go/issues/2739) 在哪一个版本解决掉了呢?
   > 
   > session Already Closed github.com/apache/dubbo-getty.init :1 runtime.doInit1 /usr/local/go/src/runtime/proc.go:7353 runtime.doInit /usr/local/go/src/runtime/proc.go:7320 runtime.main /usr/local/go/src/runtime/proc.go:254 runtime.goexit /usr/local/go/src/runtime/asm_amd64.s:1700
   > 
   > xxx/xxx/xxx/ai/pkg/transporter/dubbo.Invoke /compile/src/pkg/transporter/dubbo/generic_invoke.go:68 tuya.com/xxx/xxx/ai/pkg/transporter/dubbo.InvokeAndDecoded[...] /compile/src/pkg/transporter/dubbo/generic_invoke.go:83 tuya.com/xxx/xxx/ai/pkg/transporter/dubbo.ProxyInvoke[...] /compile/src/pkg/transporter/dubbo/generic_invoke_proxy.go:77 tuya.com/xxx/xxx/ai/pkg/infra.(*jwtKeypairManager).getPublicKeyBySecretId /compile/src/pkg/infra/jwt_keypair.go:137 tuya.com/xxx/xxx/ai/pkg/infra.GetPublicKeyForJwt /compile/src/pkg/infra/jwt_keypair.go:88 tuya.com/xxx/xxx/ai/pkg/infra.VerifyTenantJwtToken /compile/src/pkg/infra/jwt_keypair.go:232 tuya.com/xxx/xxx/ai/pkg/proxy_mcp.initStreamableMcpServerM3.VerifyMiddleware.TokenVerify.func9 /compile/src/pkg/proxy_mcp/mcp_token_verify.go:41
   
   [#2739](https://github.com/apache/dubbo-go/issues/2739) 但我没有得到有用的信息,是否可以帮我追踪一下,万分感谢


-- 
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-unsubscribe@dubbo.apache.org

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


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


Re: [I] [BUG] 泛化调用报session Already Closed 客户端无法自动恢复 [dubbo-go]

Posted by "drama10096 (via GitHub)" <gi...@apache.org>.
drama10096 commented on issue #2981:
URL: https://github.com/apache/dubbo-go/issues/2981#issuecomment-3488763181

   昨天查看这个文档时候发现,确实 https://cn.dubbo.apache.org/zh-cn/overview/mannual/golang-sdk/refer/generic/  内容有变更,晚些我对齐文档上改造观察一下


-- 
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-unsubscribe@dubbo.apache.org

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


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


Re: [I] [BUG] 泛化调用报session Already Closed 客户端无法自动恢复 [dubbo-go]

Posted by "Alanxtl (via GitHub)" <gi...@apache.org>.
Alanxtl commented on issue #2981:
URL: https://github.com/apache/dubbo-go/issues/2981#issuecomment-3488993043

   > 昨天查看这个文档时候发现,确实 https://cn.dubbo.apache.org/zh-cn/overview/mannual/golang-sdk/refer/generic/ 内容有变更,晚些我对齐文档上改造观察一下
   
   另外,我在你提到的这个老版本的示例上测试了一下 
   1. 如果使用 `dubbo.apache.org/dubbo-go/v3 v3.3.0` 版本,确实是调不通的,不过并没有报session already closed,报的是其他的错
   2. 如果使用最新的 `dubbo.apache.org/dubbo-go/v3 v3.3.1-0.20251028122905-48c55c00b702` 版本,示例调用没有问题


-- 
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-unsubscribe@dubbo.apache.org

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


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


Re: [I] [BUG] 泛化调用报session Already Closed 客户端无法自动恢复 [dubbo-go]

Posted by "drama10096 (via GitHub)" <gi...@apache.org>.
drama10096 commented on issue #2981:
URL: https://github.com/apache/dubbo-go/issues/2981#issuecomment-3484350517

   go-调用java侧dubbo微服务,经常出现“dubbo微服务重启”后session Already Closed 问题,官方到底啥时候修复啊?


-- 
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-unsubscribe@dubbo.apache.org

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


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


Re: [I] [BUG] 泛化调用报session Already Closed 客户端无法自动恢复 [dubbo-go]

Posted by "drama10096 (via GitHub)" <gi...@apache.org>.
drama10096 commented on issue #2981:
URL: https://github.com/apache/dubbo-go/issues/2981#issuecomment-3434813029

   按照官方的泛化调用使用姿势也遇到这个问题,历史上好像有人也提过这个 https://github.com/apache/dubbo-go/issues/2739  在哪一个版本解决掉了呢?
   
   session Already Closed
   github.com/apache/dubbo-getty.init
   	<autogenerated>:1
   runtime.doInit1
   	/usr/local/go/src/runtime/proc.go:7353
   runtime.doInit
   	/usr/local/go/src/runtime/proc.go:7320
   runtime.main
   	/usr/local/go/src/runtime/proc.go:254
   runtime.goexit
   	/usr/local/go/src/runtime/asm_amd64.s:1700
   
   xxx/xxx/xxx/ai/pkg/transporter/dubbo.Invoke
   /compile/src/pkg/transporter/dubbo/generic_invoke.go:68
   tuya.com/xxx/xxx/ai/pkg/transporter/dubbo.InvokeAndDecoded[...]
   /compile/src/pkg/transporter/dubbo/generic_invoke.go:83
   tuya.com/xxx/xxx/ai/pkg/transporter/dubbo.ProxyInvoke[...]
   /compile/src/pkg/transporter/dubbo/generic_invoke_proxy.go:77
   tuya.com/xxx/xxx/ai/pkg/infra.(*jwtKeypairManager).getPublicKeyBySecretId
   /compile/src/pkg/infra/jwt_keypair.go:137
   tuya.com/xxx/xxx/ai/pkg/infra.GetPublicKeyForJwt
   /compile/src/pkg/infra/jwt_keypair.go:88
   tuya.com/xxx/xxx/ai/pkg/infra.VerifyTenantJwtToken
   /compile/src/pkg/infra/jwt_keypair.go:232
   tuya.com/xxx/xxx/ai/pkg/proxy_mcp.initStreamableMcpServerM3.VerifyMiddleware.TokenVerify.func9
   /compile/src/pkg/proxy_mcp/mcp_token_verify.go:41


-- 
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-unsubscribe@dubbo.apache.org

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


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


Re: [I] [BUG] 泛化调用报session Already Closed 客户端无法自动恢复 [dubbo-go]

Posted by "Alanxtl (via GitHub)" <gi...@apache.org>.
Alanxtl commented on issue #2981:
URL: https://github.com/apache/dubbo-go/issues/2981#issuecomment-3530683756

   复现成功,怀疑是连接池的问题和链接销毁的问题
   ```
   2025/11/14 11:15:53 Connected to 10.63.116.1:2181
   2025/11/14 11:15:53 Authenticated: id=72057607807041573, timeout=4000
   2025/11/14 11:15:53 Re-submitting `0` credentials after reconnect
   2025/11/14 11:15:53 Authenticated: id=72057607807041574, timeout=5000
   2025/11/14 11:15:53 Re-submitting `0` credentials after reconnect
   2025-11-14 11:15:53	INFO	servicediscovery/service_discovery_registry.go:237	Find initial mapping applications "HashSet\ndubbo.io" for service org.apache.dubbo.samples.UserProvider.
   2025-11-14 11:15:53	INFO	zookeeper/client.go:53	[Zookeeper Client] New zookeeper client with name = 10.63.116.1:2181, zkAddress = 10.63.116.1:2181, timeout = 5s
   2025-11-14 11:15:53	INFO	servicediscovery/service_discovery_registry.go:262	Synchronized instance notification on application dubbo.io subscription, instance list size %!s(int=2)
   2025-11-14 11:15:53	INFO	servicediscovery/service_instances_changed_listener_impl.go:100	Received instance notification event of service dubbo.io, instance list size 2
   2025-11-14 11:15:53	INFO	getty/getty_client.go:76	se default getty client config
   2025-11-14 11:15:56	INFO	dubbo-getty@v1.4.10/client.go:346	net.DialTimeout(addr:10.244.0.35:20000, timeout:3e+09) = error:dial tcp 10.244.0.35:20000: i/o timeout
   github.com/apache/dubbo-getty.(*client).dialTCP
   	/home/lxt/go/pkg/mod/github.com/apache/dubbo-getty@v1.4.10/client.go:173
   github.com/apache/dubbo-getty.(*client).dial
   	/home/lxt/go/pkg/mod/github.com/apache/dubbo-getty@v1.4.10/client.go:346
   github.com/apache/dubbo-getty.(*client).connect
   	/home/lxt/go/pkg/mod/github.com/apache/dubbo-getty@v1.4.10/client.go:384
   github.com/apache/dubbo-getty.(*client).reConnect
   	/home/lxt/go/pkg/mod/github.com/apache/dubbo-getty@v1.4.10/client.go:441
   github.com/apache/dubbo-getty.(*client).RunEventLoop
   	/home/lxt/go/pkg/mod/github.com/apache/dubbo-getty@v1.4.10/client.go:419
   runtime.goexit
   	/usr/local/go/src/runtime/asm_amd64.s:1693
   2025-11-14 11:15:56	ERROR	getty/getty_client.go:195	ry to connect server 10.244.0.35:20000 failed for : failed to create client connection to 10.244.0.35:20000 in 3s
   2025-11-14 11:15:56	INFO	getty/getty_client.go:76	se default getty client config
   2025-11-14 11:15:56	WARN	dubbo-getty@v1.4.10/client.go:419	client{peer:10.244.0.35:20000} goroutine exit now.
   2025-11-14 11:15:59	INFO	dubbo-getty@v1.4.10/client.go:346	net.DialTimeout(addr:10.244.0.35:20000, timeout:3e+09) = error:dial tcp 10.244.0.35:20000: i/o timeout
   github.com/apache/dubbo-getty.(*client).dialTCP
   	/home/lxt/go/pkg/mod/github.com/apache/dubbo-getty@v1.4.10/client.go:173
   github.com/apache/dubbo-getty.(*client).dial
   	/home/lxt/go/pkg/mod/github.com/apache/dubbo-getty@v1.4.10/client.go:346
   github.com/apache/dubbo-getty.(*client).connect
   	/home/lxt/go/pkg/mod/github.com/apache/dubbo-getty@v1.4.10/client.go:384
   github.com/apache/dubbo-getty.(*client).reConnect
   	/home/lxt/go/pkg/mod/github.com/apache/dubbo-getty@v1.4.10/client.go:441
   github.com/apache/dubbo-getty.(*client).RunEventLoop
   	/home/lxt/go/pkg/mod/github.com/apache/dubbo-getty@v1.4.10/client.go:419
   runtime.goexit
   	/usr/local/go/src/runtime/asm_amd64.s:1693
   2025-11-14 11:15:59	ERROR	getty/getty_client.go:195	ry to connect server 10.244.0.35:20000 failed for : failed to create client connection to 10.244.0.35:20000 in 3s
   2025-11-14 11:15:59	ERROR	remoting/exchange_client.go:92Failed to connect server %+v 10.244.0.35:20000
   2025-11-14 11:15:59	WARN	dubbo/dubbo_protocol.go:95	an't dial the server: 10.244.0.35:20000
   2025-11-14 11:15:59	WARN	servicediscovery/service_discovery_registry.go:268	[ServiceDiscoveryRegistry] ServiceInstancesChangedListenerImpl handle error:can not connect to remote metadata service host: 10.244.0.35
   2025-11-14 11:15:59	INFO	servicediscovery/service_discovery_registry.go:276	Start subscribing to registry for applications :HashSet
   dubbo.io with a new go routine.
   2025-11-14 11:15:59	INFO	zookeeper/listener.go:483	Zookeeper Listener] listen dubbo path{/services/dubbo.io}
   2025-11-14 11:15:59	WARN	tag/router.go:52	[tag router] invokers from previous router is empty
   2025-11-14 11:15:59	WARN	proxy/proxy.go:213	[CallProxy] received rpc err: Failed to invoke the method $invoke. No provider available for the service dubbo://:@172.26.35.2:/?interface=org.apache.dubbo.samples.UserProvider&group=&version= from registry service-discovery-registry://10.63.116.1:2181?registry=zookeeper&registry.group=&registry.id=zk&registry.label=true&registry.namespace=&registry.preferred=false&registry.role=0&registry.timeout=5s&registry.ttl=15m&registry.type=&registry.weight=0&registry.zone=&remote-client-name=dubbo.registries-zookeeper-10.63.116.1%3A2181&simplified=false on the consumer 172.26.35.2 using the dubbo version 3.2.0 .Please check if the providers have been started and registered.
   panic: Failed to invoke the method $invoke. No provider available for the service dubbo://:@172.26.35.2:/?interface=org.apache.dubbo.samples.UserProvider&group=&version= from registry service-discovery-registry://10.63.116.1:2181?registry=zookeeper&registry.group=&registry.id=zk&registry.label=true&registry.namespace=&registry.preferred=false&registry.role=0&registry.timeout=5s&registry.ttl=15m&registry.type=&registry.weight=0&registry.zone=&remote-client-name=dubbo.registries-zookeeper-10.63.116.1%3A2181&simplified=false on the consumer 172.26.35.2 using the dubbo version 3.2.0 .Please check if the providers have been started and registered.
   
   goroutine 1 [running]:
   main.callGetUser({0xc000336fa0, {0x1eaed50, 0xc000614e40}, {0xc0000f2120, 0x1, 0x1}, 0xc0004bce70, {0x1bd4554, 0x8}, {0x1c0a34a, ...}, ...})
   	/home/lxt/repo/dubbo-go-samples/generic/default/go-client/cmd/client.go:73 +0x571
   main.main()
   	/home/lxt/repo/dubbo-go-samples/generic/default/go-client/cmd/client.go:46 +0xc5
   exit status 2
   ```


-- 
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-unsubscribe@dubbo.apache.org

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


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


Re: [I] [BUG] 泛化调用报session Already Closed 客户端无法自动恢复 [dubbo-go]

Posted by "Alanxtl (via GitHub)" <gi...@apache.org>.
Alanxtl commented on issue #2981:
URL: https://github.com/apache/dubbo-go/issues/2981#issuecomment-3690739729

   > > hi [@drama10096](https://github.com/drama10096) [@vipyxc-byte](https://github.com/vipyxc-byte) this bug is fixed in [#3071](https://github.com/apache/dubbo-go/pull/3071), try this
   > > this bug was introduced in [#2726](https://github.com/apache/dubbo-go/pull/2726), the operation of `bi.url` set to nil and the access of url in `cluster/cluster/failover/cluster_invoker.go: 86` may happen concurrently, thus cause nil pointer access
   > > ```
   > > func (bi *BaseInvoker) Destroy() {
   > > 	logger.Infof("Destroy invoker: %s", bi.GetURL())
   > > 	bi.destroyed.Store(true)
   > > 	bi.available.Store(false)
   > > 	bi.url = nil
   > > }
   > > ```
   > > 
   > > 
   > >     
   > >       
   > >     
   > > 
   > >       
   > >     
   > > 
   > >     
   > >   
   > > k8s集群内的测试我也试过了 应该是没问题的
   > > session already close 的问题我没复现出来 但是上文提到的偶发的panic在这个pr中被修复了
   > 
   > 大佬,上次提到的偶发panic计划什么时候发布?
   
   这周或者下周应该就会发了,肯定会在年前发的,现在正在排期


-- 
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-unsubscribe@dubbo.apache.org

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


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


Re: [I] [BUG] 泛化调用报session Already Closed 客户端无法自动恢复 [dubbo-go]

Posted by "vipyxc-byte (via GitHub)" <gi...@apache.org>.
vipyxc-byte commented on issue #2981:
URL: https://github.com/apache/dubbo-go/issues/2981#issuecomment-3235479858

   补充rpc服务加载逻辑(如需提供源码,再联系哦):
   1. dubbogo.yaml是我通过koanf.Koanf加载的,序列化为rpcTransporter实例
   2. 将Consumer转换GenericApi,初始化referenceCache的references,key是GenericApi的group+"/"+interfaceName+":"+version
   3. 拿到reference实例后,调用reference的load方法加载rpc服务,并赋值给reference的rf属性
   
   ```
   type rpcTransporter struct {
   	// Consumer不参与config.loadReference
   	// 获取registryIds/RequestTimeout/References
   	Consumer   *config.ConsumerConfig `yaml:"consumer" json:"consumer" property:"consumer"`
           references *referenceCache
   }
   type referenceCache struct { // 自定义缓存
   	references map[string]*reference // key:group+"/"+interfaceName+":"+version
   	lock       sync.RWMutex // 保证 references 的并发安全
   }
   type reference struct { // 泛化服务的包装
   	lock sync.Mutex              // 保证 rf 的并发安全
   	rf   *config.ReferenceConfig // 泛化服务的引用
   }
   type GenericApi struct { // consumer转为自定义的GenericApi,进行rpc服务的加载
   	application   string // 所属应用
   	protocol      string // 协议,必须
   	interfaceName string // 接口名,必须
   	version       string // 版本
   	group         string // 分组
   	timeout       string // 超时时间,注意要带单位,例如:5s
   	retries       string // 重试次数
   	waitForInitSecond time.Duration // 静态注册的dubbo消费者初始化的时间,单位:秒,动态注册的api等待时间是固定值
   }
   ```
   


-- 
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-unsubscribe@dubbo.apache.org

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


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


Re: [I] [BUG] 客户端访问报session Already Closed 客户端消费者无法自动恢复 [dubbo-go]

Posted by "vipyxc-byte (via GitHub)" <gi...@apache.org>.
vipyxc-byte commented on issue #2981:
URL: https://github.com/apache/dubbo-go/issues/2981#issuecomment-3212917787

   rpc服务加载代码:
   
   `func (r *reference) load(api *GenericApi, trace logger.Logger) (common.RPCService, error) {
   	r.lock.Lock()
   	defer r.lock.Unlock()
   	refId := api.RefId()
   
   	if r.rf != nil {
   		return r.rf.GetRPCService(), nil
   	}
   
   	if api.protocol == "" {
   		api.protocol = constant.Dubbo
   	}
   
   	if api.timeout == "" {
   		api.timeout = t.Consumer.RequestTimeout
   	}
   
   	if api.retries == "" {
   		api.retries = "0"
   	}
   
   	r.rf = config.NewReferenceConfigBuilder().
   		SetInterface(api.interfaceName).
   		SetGroup(api.group).
   		SetVersion(api.version).
   		SetRequestTimeout(api.timeout).
   		SetRetries(api.retries).
   		SetProtocol(api.protocol).
   		SetRegistryIDs(t.Consumer.RegistryIDs...).
   		SetGeneric(true).
   		SetSerialization(constant.Hessian2Serialization).
   		SetLoadbalance(constant.LoadBalanceKeyRandom).
   		SetCluster(constant.ClusterKeyFailover).
   		Build()
   	rootConfig := config.GetRootConfig()
   	err := r.rf.Init(rootConfig)
   	if err != nil {
   		return nil, err
   	}
   
   	// v3.2.0-rc1 refConf.GenericLoad(refId)存在bug,需要手动创建和关联相关的GenericService
   	// v3.3.0 修复了这个bug,直接使用refConf.GenericLoad(refId)即可
   	// refConf.GenericLoad(refId)
   	// 自维护,所以手动创建和关联GenericService,而且不需要 onfig.SetConsumerService(gs)
   	gs := generic.NewGenericService(refId)
   	r.rf.Refer(gs)
   	r.rf.Implement(gs)
   	// config.SetConsumerService(gs)
   
   	waitTime := api.waitForInitSecond
   	if waitTime <= 0 {
   		waitTime = 5 * time.Second
   	}
   
   	timeout, cancel := context.WithTimeout(context.Background(), waitTime)
   	defer cancel()
   	index := 0
   end:
   	for {
   		index++
   		select {
   		case <-timeout.Done():
   			trace.Warn("dubbo rpc service load timeout")
   			break end
   		default:
   			b := r.recheck(r.rf.GetInvoker(), trace)
   			if b {
   				trace.Infof("dubbo rpc service load success, recheck count: %d", index)
   				break end
   			}
   			time.Sleep(1 * time.Second)
   		}
   	}
   	return r.rf.GetRPCService(), nil
   }
   
   // recheck 检查invoker是否可用
   func (r *reference) recheck(invoker protocol.Invoker, trace logger.Logger) bool {
   	defer func() {
   		// invoker.IsAvailable 逻辑中可能会有 panic: runtime error: invalid memory address or nil pointer dereference
   		if r := recover(); r != nil {
   			trace.Info("generic service not ready, wait for next check")
   		}
   	}()
   	if !invoker.IsAvailable() {
   		return false
   	}
   	return true
   }`


-- 
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-unsubscribe@dubbo.apache.org

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


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


Re: [I] [BUG] 泛化调用报session Already Closed 客户端无法自动恢复 [dubbo-go]

Posted by "vipyxc-byte (via GitHub)" <gi...@apache.org>.
vipyxc-byte commented on issue #2981:
URL: https://github.com/apache/dubbo-go/issues/2981#issuecomment-3701780148

   panic: runtime error: invalid memory address or nil pointer dereference
   [signal SIGSEGV: segmentation violation code=0x2 addr=0x0 pc=0x102a668f8]
   
   goroutine 3809079 [running]:
   dubbo.apache.org/dubbo-go/v3/common.(*URL).GetParam(0x0, {0x1045bd638, 0xb}, {0x0, 0x0})
   	/Users/dev/go/pkg/mod/dubbo.apache.org/dubbo-go/v3@v3.3.1/common/url.go:608 +0x38
   dubbo.apache.org/dubbo-go/v3/cluster/router/tag.(*PriorityRouter).Notify(0x1414fe18c60, {0x140b6945170, 0x1, 0x1})
   	/Users/dev/go/pkg/mod/dubbo.apache.org/dubbo-go/v3@v3.3.1/cluster/router/tag/router.go:80 +0x84
   dubbo.apache.org/dubbo-go/v3/cluster/router/chain.(*RouterChain).SetInvokers(0x140f6b38720, {0x140b6945170, 0x1, 0x1})
   	/Users/dev/go/pkg/mod/dubbo.apache.org/dubbo-go/v3@v3.3.1/cluster/router/chain/chain.go:95 +0x1a4
   dubbo.apache.org/dubbo-go/v3/registry/directory.(*RegistryDirectory).setNewInvokers(0x140b0e65d90)
   	/Users/dev/go/pkg/mod/dubbo.apache.org/dubbo-go/v3@v3.3.1/registry/directory/directory.go:344 +0x148
   dubbo.apache.org/dubbo-go/v3/registry/directory.(*RegistryDirectory).refreshInvokers(0x140b0e65d90, 0x1416408ea80)
   	/Users/dev/go/pkg/mod/dubbo.apache.org/dubbo-go/v3@v3.3.1/registry/directory/directory.go:241 +0x1b4
   dubbo.apache.org/dubbo-go/v3/registry/directory.(*RegistryDirectory).Notify(0x140b0e65d90, 0x1416408ea80)
   	/Users/dev/go/pkg/mod/dubbo.apache.org/dubbo-go/v3@v3.3.1/registry/directory/directory.go:219 +0x44
   dubbo.apache.org/dubbo-go/v3/registry.(*BaseRegistry).Subscribe(0x14000ab90e0, 0x140b14d61c0, {0x104f49fd0, 0x140b0e65d90})
   	/Users/dev/go/pkg/mod/dubbo.apache.org/dubbo-go/v3@v3.3.1/registry/base_registry.go:354 +0x44c
   dubbo.apache.org/dubbo-go/v3/registry/directory.(*RegistryDirectory).Subscribe.func1()
   	/Users/dev/go/pkg/mod/dubbo.apache.org/dubbo-go/v3@v3.3.1/registry/directory/directory.go:167 +0x8c
   created by dubbo.apache.org/dubbo-go/v3/registry/directory.(*RegistryDirectory).Subscribe in goroutine 1640288
   	/Users/dev/go/pkg/mod/dubbo.apache.org/dubbo-go/v3@v3.3.1/registry/directory/directory.go:165 +0x160
   
   @Alanxtl 升级了3.3.1,开100个协程,每个协程都for循环调用服务,同时代码中定时调用ReferenceConfig.GetInvoker().Destroy(),使代码可以重新构建ReferenceConfig。运行一段时间出现上述问题。


-- 
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-unsubscribe@dubbo.apache.org

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


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


Re: [I] [BUG] 泛化调用报session Already Closed 客户端无法自动恢复 [dubbo-go]

Posted by "Alanxtl (via GitHub)" <gi...@apache.org>.
Alanxtl commented on issue #2981:
URL: https://github.com/apache/dubbo-go/issues/2981#issuecomment-3531198749

   hi @drama10096 @vipyxc-byte 
   this bug is fixed in https://github.com/apache/dubbo-go/pull/3071, try this
   
   
   
   this bug was introduced in https://github.com/apache/dubbo-go/pull/2726, the operation of `bi.url` set to nil and the access of url in `cluster/cluster/failover/cluster_invoker.go: 86` may happen concurrently, thus cause nil pointer access
   ```
   func (bi *BaseInvoker) Destroy() {
   	logger.Infof("Destroy invoker: %s", bi.GetURL())
   	bi.destroyed.Store(true)
   	bi.available.Store(false)
   	bi.url = nil
   }
   ```


-- 
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-unsubscribe@dubbo.apache.org

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


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


Re: [I] [BUG] 泛化调用报session Already Closed 客户端无法自动恢复 [dubbo-go]

Posted by "vipyxc-byte (via GitHub)" <gi...@apache.org>.
vipyxc-byte commented on issue #2981:
URL: https://github.com/apache/dubbo-go/issues/2981#issuecomment-3537746783

   > hi [@drama10096](https://github.com/drama10096) [@vipyxc-byte](https://github.com/vipyxc-byte) this bug is fixed in [#3071](https://github.com/apache/dubbo-go/pull/3071), try this
   > 
   > this bug was introduced in [#2726](https://github.com/apache/dubbo-go/pull/2726), the operation of `bi.url` set to nil and the access of url in `cluster/cluster/failover/cluster_invoker.go: 86` may happen concurrently, thus cause nil pointer access
   > 
   > ```
   > func (bi *BaseInvoker) Destroy() {
   > 	logger.Infof("Destroy invoker: %s", bi.GetURL())
   > 	bi.destroyed.Store(true)
   > 	bi.available.Store(false)
   > 	bi.url = nil
   > }
   > ```
   > 
   > k8s集群内的测试我也试过了 应该是没问题的
   > 
   > session already close 的问题我没复现出来 但是上文提到的偶发的panic在这个pr中被修复了
   
    session already close是频繁发布服务端偶现的,复现不出来的话,那我等偶发panic的pr发布后再通过destory+重建ref的方式尝试绕过session already close的问题,如果并发情况下问题得以解决,我会将方案同步到这里。感谢大佬的支持!


-- 
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-unsubscribe@dubbo.apache.org

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


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


Re: [I] [BUG] 泛化调用报session Already Closed 客户端无法自动恢复 [dubbo-go]

Posted by "HGD-coder (via GitHub)" <gi...@apache.org>.
HGD-coder commented on issue #2981:
URL: https://github.com/apache/dubbo-go/issues/2981#issuecomment-3762917346

   > panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x2 addr=0x0 pc=0x102a668f8]
   > 
   > goroutine 3809079 [running]: dubbo.apache.org/dubbo-go/v3/common.(*URL).GetParam(0x0, {0x1045bd638, 0xb}, {0x0, 0x0}) /Users/dev/go/pkg/mod/dubbo.apache.org/dubbo-go/v3@v3.3.1/common/url.go:608 +0x38 dubbo.apache.org/dubbo-go/v3/cluster/router/tag.(*PriorityRouter).Notify(0x1414fe18c60, {0x140b6945170, 0x1, 0x1}) /Users/dev/go/pkg/mod/dubbo.apache.org/dubbo-go/v3@v3.3.1/cluster/router/tag/router.go:80 +0x84 dubbo.apache.org/dubbo-go/v3/cluster/router/chain.(*RouterChain).SetInvokers(0x140f6b38720, {0x140b6945170, 0x1, 0x1}) /Users/dev/go/pkg/mod/dubbo.apache.org/dubbo-go/v3@v3.3.1/cluster/router/chain/chain.go:95 +0x1a4 dubbo.apache.org/dubbo-go/v3/registry/directory.(*RegistryDirectory).setNewInvokers(0x140b0e65d90) /Users/dev/go/pkg/mod/dubbo.apache.org/dubbo-go/v3@v3.3.1/registry/directory/directory.go:344 +0x148 dubbo.apache.org/dubbo-go/v3/registry/directory.(*RegistryDirectory).refreshInvokers(0x140b0e65d90, 0x1416408ea80) /Users/dev/go/pkg/mod/dubbo.apache.org/dubbo-go/v3
 @v3.3.1/registry/directory/directory.go:241 +0x1b4 dubbo.apache.org/dubbo-go/v3/registry/directory.(*RegistryDirectory).Notify(0x140b0e65d90, 0x1416408ea80) /Users/dev/go/pkg/mod/dubbo.apache.org/dubbo-go/v3@v3.3.1/registry/directory/directory.go:219 +0x44 dubbo.apache.org/dubbo-go/v3/registry.(*BaseRegistry).Subscribe(0x14000ab90e0, 0x140b14d61c0, {0x104f49fd0, 0x140b0e65d90}) /Users/dev/go/pkg/mod/dubbo.apache.org/dubbo-go/v3@v3.3.1/registry/base_registry.go:354 +0x44c dubbo.apache.org/dubbo-go/v3/registry/directory.(*RegistryDirectory).Subscribe.func1() /Users/dev/go/pkg/mod/dubbo.apache.org/dubbo-go/v3@v3.3.1/registry/directory/directory.go:167 +0x8c created by dubbo.apache.org/dubbo-go/v3/registry/directory.(*RegistryDirectory).Subscribe in goroutine 1640288 /Users/dev/go/pkg/mod/dubbo.apache.org/dubbo-go/v3@v3.3.1/registry/directory/directory.go:165 +0x160
   > 
   > [@Alanxtl](https://github.com/Alanxtl) 升级了3.3.1,开100个协程,每个协程都for循环调用服务,同时代码中定时调用ReferenceConfig.GetInvoker().Destroy(),使代码可以重新构建ReferenceConfig。运行一段时间出现上述问题。
   
   @vipyxc-byte 请问可以提供这个情况的最小可复现示例吗?或者描述详细全面一些,让我自己可以本地复现一下。
   


-- 
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-unsubscribe@dubbo.apache.org

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


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


Re: [I] [BUG] 泛化调用报session Already Closed 客户端无法自动恢复 [dubbo-go]

Posted by "drama10096 (via GitHub)" <gi...@apache.org>.
drama10096 commented on issue #2981:
URL: https://github.com/apache/dubbo-go/issues/2981#issuecomment-3485559540

   https://cn.dubbo.apache.org/zh-cn/overview/mannual/golang-sdk/refer/generic/   早期(25年初)是基于这个文档实现的


-- 
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-unsubscribe@dubbo.apache.org

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


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


Re: [I] [BUG] 泛化调用报session Already Closed 客户端无法自动恢复 [dubbo-go]

Posted by "Alanxtl (via GitHub)" <gi...@apache.org>.
Alanxtl commented on issue #2981:
URL: https://github.com/apache/dubbo-go/issues/2981#issuecomment-3514867912

   > 服务端频繁重启会导致这样的情况,我在本地测试没有模拟出,但是k8s频繁重启/发布会导致session Already Closed
   
   hi @vipyxc-byte 感谢回复
   这个我想想在本地怎么复现吧,不过看起来似乎不太好复现,如果有好的建议可以继续跟进
   


-- 
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-unsubscribe@dubbo.apache.org

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


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


Re: [I] [BUG] 泛化调用报session Already Closed 客户端无法自动恢复 [dubbo-go]

Posted by "vipyxc-byte (via GitHub)" <gi...@apache.org>.
vipyxc-byte commented on issue #2981:
URL: https://github.com/apache/dubbo-go/issues/2981#issuecomment-3689261390

   > hi [@drama10096](https://github.com/drama10096) [@vipyxc-byte](https://github.com/vipyxc-byte) this bug is fixed in [#3071](https://github.com/apache/dubbo-go/pull/3071), try this
   > 
   > this bug was introduced in [#2726](https://github.com/apache/dubbo-go/pull/2726), the operation of `bi.url` set to nil and the access of url in `cluster/cluster/failover/cluster_invoker.go: 86` may happen concurrently, thus cause nil pointer access
   > 
   > ```
   > func (bi *BaseInvoker) Destroy() {
   > 	logger.Infof("Destroy invoker: %s", bi.GetURL())
   > 	bi.destroyed.Store(true)
   > 	bi.available.Store(false)
   > 	bi.url = nil
   > }
   > ```
   > 
   > k8s集群内的测试我也试过了 应该是没问题的
   > 
   > session already close 的问题我没复现出来 但是上文提到的偶发的panic在这个pr中被修复了
   
   大佬,上次提到的偶发panic计划什么时候发布?


-- 
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-unsubscribe@dubbo.apache.org

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


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