News for hackers. Stuff that matters.
Re:ZeroMQ instead of HTTP, for internal services by rumcajz on Tuesday July 23, 2013 @04:55AM (#6088923)
It's a TCP issue. When the other end of the connection goes away silently (power goes of, cable is cut off etc.) TCP doesn't inform ZeroMQ that the connection is broken, so ZeroMQ uses it furthe without trying to handle the error.
Re:ZeroMQ instead of HTTP, for internal services by jzwinck on Tuesday July 23, 2013 @09:50AM (#6089972)
It's only an issue with TCP if you forget to enable keep-alive (http://www.gnugk.org/keepalive.html). Keep-alive solves this problem, and it solves other problems too, like when your network equipment decides a connection is no longer needed and disables it. Or, you can implement application-level heartbeats--whenever you send you have the chance to recognize that your peer has gone away.
Re:ZeroMQ instead of HTTP, for internal services by bluesmoon on Thursday July 25, 2013 @01:19AM (#6101043)
That's an interesting thought. I need to look into whether I have TCP keepalive turned on for my private interfaces.
Re:ZeroMQ instead of HTTP, for internal services by mh- on Tuesday July 23, 2013 @06:00AM (#6089092)
I'd call that a characteristic of TCP, not an 'issue'.