You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "James E. King, III (JIRA)" <ji...@apache.org> on 2017/05/05 14:41:04 UTC
[jira] [Comment Edited] (THRIFT-4188) Error while flushing write
buffer of size 70 to transport, only wrote 0 bytes: write tcp
127.0.0.1:5000->127.0.0.1:58174: write: broken pipe
[ https://issues.apache.org/jira/browse/THRIFT-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15998418#comment-15998418 ]
James E. King, III edited comment on THRIFT-4188 at 5/5/17 2:40 PM:
--------------------------------------------------------------------
Any chance you could attach a .go source code file that shows the behavior along with the thrift file that drives it?
I don't understand go very well right now, but I would be willing to use this opportunity to learn a little bit.
was (Author: jking3):
Any chance you could attach a .go source code file that shows the behavior?
I don't understand go very well right now, but I would be willing to use this opportunity to learn a little bit.
> Error while flushing write buffer of size 70 to transport, only wrote 0 bytes: write tcp 127.0.0.1:5000->127.0.0.1:58174: write: broken pipe
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: THRIFT-4188
> URL: https://issues.apache.org/jira/browse/THRIFT-4188
> Project: Thrift
> Issue Type: Bug
> Components: Go - Library
> Affects Versions: 0.10.0
> Reporter: brian.kang
>
> if *server {
> if err := runServer(transportFactory, protocolFactory, *addr, *secure); err != nil {
> fmt.Println("error running server:", err)
> }
> } else {
> done := make(chan int32)
> for i := 0; i < 5000; i++ {
> go func(i int) {
> err, s := runClient(transportFactory, protocolFactory, *addr, *secure, int32(i))
> if err != nil {
> fmt.Println("error running client:", err)
> }
> done <- s
> }(i)
> }
> for i := 0; i < 5000; i++ {
> fmt.Println(<-done)
> }
> }
> too many errors,eg:
> Error while flushing write buffer of size 17 to transport, only wrote 02017/05/04 13:29:00 error processing request: write tcp 127.0.0.1:9090->127.0.0.1:58932: write: broken pipe
> bytes: write tcp 127.0.0.1:9090->127.0.0.1:58915: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 127.0.0.1:9090->127.0.0.1:58922: write: broken pipe
> Error while flushing write buffer of size 2017/05/04 13:29:00 error processing request: write tcp 127.0.0.1:9090->127.0.0.1:58928: write: broken pipe
> 17 to transport, only wrote 0 bytes: write tcp 127.0.0.1:9090->127.0.0.1:58923: write: broken pipe2017/05/04 13:29:00 error processing request: write tcp 127.0.0.1:9090->127.0.0.1:58915: write: broken pipe
> Error while flushing write buffer of size 17 to transport, only wrote 0 bytes: write tcp 127.0.0.1:9090->127.0.0.1:58930: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 127.0.0.1:9090->127.0.0.1:58923: write: broken pipe
> Error while flushing write buffer of size 17 to transport, only wrote 0 bytes: write tcp 127.0.0.1:9090->127.0.0.1:58926: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 127.0.0.1:9090->127.0.0.1:58930: write: broken pipe
> Error while flushing write buffer of size 2017/05/04 13:29:00 error processing request: write tcp 127.0.0.1:9090->127.0.0.1:58923: write: broken pipe
> 17 to transport, only wrote 0 bytes: write tcp 127.0.0.1:9090->127.0.0.1:58920: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 127.0.0.1:9090->127.0.0.1:58932: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 127.0.0.1:9090->127.0.0.1:58930: write: broken pipe
> Error while flushing write buffer of size 17 to transport, only wrote 2017/05/04 13:29:00 error processing request: write tcp 127.0.0.1:9090->127.0.0.1:58926: write: broken pipe
> 0 bytes: write tcp 127.0.0.1:9090->127.0.0.1:58912: write: broken pipe
> Error while flushing write buffer of size 172017/05/04 13:29:00 error processing request: write tcp 127.0.0.1:9090->127.0.0.1:58912: write: broken pipe
> to transport, only wrote 0 bytes: write tcp 127.0.0.1:9090->127.0.0.1:58918: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 127.0.0.1:9090->127.0.0.1:58918: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 127.0.0.1:9090->127.0.0.1:58920: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 127.0.0.1:9090->127.0.0.1:58920: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 127.0.0.1:9090->127.0.0.1:58915: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 127.0.0.1:9090->127.0.0.1:58912: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 127.0.0.1:9090->127.0.0.1:58918: write: broken pipe
> 2017/05/04 13:29:00 error processing request: write tcp 127.0.0.1:9090->127.0.0.1:58926: write: broken pipe
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)