You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
send rpc request with client.Call(ctx, req, rsp, opts ....) method, one is ok ,one failed
first request ok , second request failed with : {"id":"go.micro.client.transport","code":500,"detail":"readfrom tcp 192.168.240.26:51266-\u003e192.168.240.32:45054: write tcp 192.168.240.26:51266-\u003e192.168.240.32:45054: write: broken pipe","status":"Internal Server Error"}
then third request ok , fourth failed with same err {"id":"go.micro.client.transport","code":500,"detail":"readfrom tcp 192.168.240.26:51266-\u003e192.168.240.32:45054: write tcp 192.168.240.26:51266-\u003e192.168.240.32:45054: write: broken pipe","status":"Internal Server Error"}
fifth is ok ,and sixth failed with same err {"id":"go.micro.client.transport","code":500,"detail":"readfrom tcp 192.168.240.26:51266-\u003e192.168.240.32:45054: write tcp 192.168.240.26:51266-\u003e192.168.240.32:45054: write: broken pipe","status":"Internal Server Error"}
then same result ...
What are you trying to do?
when version v2.9.2: local and centos7.9 docker all ok
then upgrade to v4.10.2 : local ok , but centos7.9 docker failed
same code , in my local wiindows matchine is ok , then deploy in centos7.9 with docker , occoured that error
What did you expect to happen?
expect every request is ok
What happens instead?
one is ok , one failed
How to reproduce the bug
upgrade from v2.9.2 to v4.10.2
browser http request -> custom gateway -> rpc call service A
Describe the bug
send rpc request with client.Call(ctx, req, rsp, opts ....) method, one is ok ,one failed
first request ok , second request failed with :
{"id":"go.micro.client.transport","code":500,"detail":"readfrom tcp 192.168.240.26:51266-\u003e192.168.240.32:45054: write tcp 192.168.240.26:51266-\u003e192.168.240.32:45054: write: broken pipe","status":"Internal Server Error"}
then third request ok , fourth failed with same err
{"id":"go.micro.client.transport","code":500,"detail":"readfrom tcp 192.168.240.26:51266-\u003e192.168.240.32:45054: write tcp 192.168.240.26:51266-\u003e192.168.240.32:45054: write: broken pipe","status":"Internal Server Error"}
fifth is ok ,and sixth failed with same err
{"id":"go.micro.client.transport","code":500,"detail":"readfrom tcp 192.168.240.26:51266-\u003e192.168.240.32:45054: write tcp 192.168.240.26:51266-\u003e192.168.240.32:45054: write: broken pipe","status":"Internal Server Error"}
then same result ...
What are you trying to do?
when version v2.9.2: local and centos7.9 docker all ok
then upgrade to v4.10.2 : local ok , but centos7.9 docker failed
same code , in my local wiindows matchine is ok , then deploy in centos7.9 with docker , occoured that error
What did you expect to happen?
expect every request is ok
What happens instead?
one is ok , one failed
How to reproduce the bug
upgrade from v2.9.2 to v4.10.2
browser http request -> custom gateway -> rpc call service A
gateway service send rpc with client.Call method
If possible, please include a minimal code snippet here.
Environment
Go Version: please paste
go version
output hereThe text was updated successfully, but these errors were encountered: