Further testing indicates problems
Further testing indicates problems

After the first or second ping failure, calls into zmq_poll are busy
looping, pegging a CORE at 100%. I've not been able to identify why this
is occuring and I still need a better understanding of how loop policy
providers interact with each other and if it is possible to use the
global loop policy ...

jr0d/mercury,jr0d/mercury