Closed emarcotte closed 12 years ago
This may actually be due to our load balancer configuration, but ideally we wouldn't get SIGPIPE on a bad read. I may be able to provide a pull request to fix this, but I haven't gotten that far yet.
Argh, nevermind. I've got a secret fork killing my connections. How do I close an issue?
It seems like there's some sort of heartbeat/timeout bug that I'm encountering. I have a little script waiting for messages using recv. My initial first pass was to undef my broker and reconnect, but doing so causes DESTROY to crash with SIGPIPE. Below is some GDB output.