I have encountered the same assertion before too on WinXP. I think the "another service listening on the port" possibility would cause an assert on a bind and not here?
The thing is that the user app can't do anything as zmq handles auto-reconnect. On Jan 22, 2013 4:35 AM, "Ian Barber" <[email protected]> wrote: > On Mon, Jan 21, 2013 at 9:23 AM, Pau <[email protected]> wrote: > >> etimes (mayby minutes, maybe hours) an error WSAEADDRINUSE happens. >> In line (253) some values are checked and the error is dicarded if it is >> a known error but not WSAEADDRINUSE. >> // Assert if the error was caused by 0MQ bug. >> // Networking problems are OK. No need to assert. >> > > The problem here is that your have a spurious address in use (or at least > a very short term one), but a long term address in use is an error that > needs to be handled. I'm not sure your fix is the right one, because if > there is another service listening on the port, it should error here. It is > a tricky error though, for exactly these reasons. I would be inclined in > application to spin and try again. > > 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
