On Mon, 2014-01-13 at 20:19 +0100, Julian Taylor wrote: > the underlying issue was in zeromq3 which is now fixed. Given back. Regards, Adam