[zeromq-dev] tcp_connecter Assertion failed

Brian Granger ellisonbg at gmail.com
Thu Jul 8 16:56:57 CEST 2010


Is this bug the following issue again:

http://github.com/zeromq/zeromq2/issues/unreads#issue/31

Brian

On Wed, Jun 30, 2010 at 7:02 AM, rad jan <jan.rad at gmail.com> wrote:
> Hi, folks,
> Thanks for your great work!
> We use zmq as the message system between modules on different servers.
> The servers are in an unreliable environment, e.g. I may connect to a server
> but its actual state is down or some server's network may fail for a while.
> There are two circumstances where I get assertion failed.
> 1. When I tried to connect to a server that has not started yet. (Does not
> happen all the time)
> 2. When a connected server's network is failed.
> I am using zmq2.0.7 with python binding.
> Here is some sample code:
>>>> import zmq
>>>> c = zmq.Context()
>>>> addrs = ['tcp://10.1.169.55:6666', 'tcp://10.1.169.57:6666',
>>>> 'tcp://10.1.168.210:6666']
>>>> sockets = []
>>>> for addr in addrs:
> ...     s = c.socket(zmq.XREQ)
> ...     s.connect(addr)
> ...     sockets.append(s)
>>>> Assertion failed: err == ECONNREFUSED || err == ETIMEDOUT
>>>> (tcp_connecter.cpp:296)
> Terminated (core dumped)
> Is there any way to get rid of this error?
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
>



-- 
Brian E. Granger, Ph.D.
Assistant Professor of Physics
Cal Poly State University, San Luis Obispo
bgranger at calpoly.edu
ellisonbg at gmail.com



More information about the zeromq-dev mailing list