Looks like we had similar issues in our tests and we ignored them in the test cases:
https://issues.apache.org/jira/browse/ZOOKEEPER-482 Is this the tracking jira for SIGPIPE issue? https://issues.apache.org/jira/browse/ZOOKEEPER-1051 thanks mahadev On Mon, Aug 22, 2011 at 7:44 AM, Stephen Tyree <[email protected]> wrote: > Right now when send is called after the cluster has closed the connection > (say on session expiration) SIGPIPE is fired for the entire application. > This seems like something we shouldn't be leaking out of the API, so a > simple fix (at least for Linux) would be to add the MSG_NOSIGNAL option to > any socket sends we do. This isn't portable to other platforms, but on other > platforms there are similar solutions to the problem. What does everyone > think? >
