[ https://issues.apache.org/jira/browse/THRIFT-5611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Erik updated THRIFT-5611: ------------------------- Description: I jumped from v0.15.0 to v0.16.0 .. and trying to track down what could cause this response in my C++ Server ``` {color:#000000}Thrift: Mon Aug 15 22:11:54 2022 TSocket::write_partial() send() <Host: 127.0.0.1 Port: 58998>: Broken pipe {color} 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 ``` 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? was: I jumped from v0.15.0 to v0.16.0 .. and trying to track down what could cause this response in my C++ Server ``` {color:#000000}Thrift: Mon Aug 15 22:11:54 2022 TSocket::write_partial() send() <Host: 127.0.0.1 Port: 58998>: Broken pipe {color} 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 ``` > 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 > ``` > {color:#000000}Thrift: Mon Aug 15 22:11:54 2022 TSocket::write_partial() > send() <Host: 127.0.0.1 Port: 58998>: Broken pipe {color} > 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 > ``` > 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)