[
https://issues.apache.org/jira/browse/THRIFT-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16384739#comment-16384739
]
James E. King, III commented on THRIFT-4188:
--------------------------------------------
If the go transport for ssl reports a TTransportException of type END_OF_FILE
when SIGPIPE occurs from openssl, then the go server can be taught to ignore
that condition and not record it in the log. I just made this change for
dlang, THRIFT-4503, and made it a long time ago in the C++ server.
> 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
> Priority: Major
> Attachments: client.go, handler.go, main.go, main.go, server.go,
> shared.thrift, tutorial.thrift
>
>
> {code}
> 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)
> }
> }
> {code}
> too many errors,eg:
> {code}
> 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
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
