You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Erik (Jira)" <ji...@apache.org> on 2022/08/16 13:44:00 UTC
[jira] [Closed] (THRIFT-5611) v0.16.0 C++ servers suddenly giving brokenpipe errors
[ https://issues.apache.org/jira/browse/THRIFT-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Erik closed THRIFT-5611.
------------------------
Resolution: Invalid
closing this.. the error was on my side.. I'd opened up 32 threads on a 4 core CPU... and all hell broke loose after that
> v0.16.0 C++ servers suddenly giving brokenpipe errors
> -----------------------------------------------------
>
> Key: THRIFT-5611
> URL: https://issues.apache.org/jira/browse/THRIFT-5611
> Project: Thrift
> Issue Type: Bug
> Components: C++ - Library
> Affects Versions: 0.16.0
> Reporter: Erik
> Priority: Major
>
> I jumped from v0.15.0 to v0.16.0 .. and trying to track down what could cause this response in my C++ Server
>
> {code:java}
> Thrift: Mon Aug 15 22:11:54 2022 TSocket::write_partial() send() <Host: 127.0.0.1 Port: 58998>: Broken pipe
> Thrift: Mon Aug 15 22:11:54 2022 TConnectedClient died: write() send(): Broken pipe
> Thrift: Mon Aug 15 22:11:54 2022 TConnectedClient output close failed: Called write on non-open socket
> {code}
>
> my server code is unchanged and was previously okay, I think.. I will keep debugging and trying to ensure it's not me but.. can anyone clue me in on how to repair this ? or what to look for?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)