Thanks guys, Unfortunately there is no python stack trace, it looks like the error is coming from a zeromq thread and then sending the SIGABRT up. I don't know where the conflict is coming from though. I guess I need a better understanding of some of the threading that zeromq is doing underneath the python
On Mon, Jul 9, 2012 at 2:34 PM, Ian Barber <[email protected]> wrote: > > > On Mon, Jul 9, 2012 at 9:26 PM, Thomas S Hatch <[email protected]> wrote: >> >> Actually, I should ask... >> >> The main issue we are seeing in here is that the SUB socket looses >> connection from the PUB socket when connecting over unreliable connections >> like the internet. Is there a way to detect if the SUB socket is still >> connected to the PUB socket? >> > > Sort of: Either layer a heartbeat on top, or use the ZMQ_MONITOR stuff in > ZMQ3.1+ to look for disconnect events. I suspect you'll get better accuracy > with the heartbeat (as it'll catch a multitude of sins), but monitor would > easier. > > Ian > > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > >
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
