Sorry guys it's my own fault. There is an oversight in my code - I bind() and connect() sockets sequentially but in separate threads, so it is not exactly a sequential execution. Thanks to everybody who responded. Sorry for the false alarm.
Dmitri > -----Original Message----- > From: zeromq-dev-boun...@lists.zeromq.org > [mailto:zeromq-dev-boun...@lists.zeromq.org] On Behalf Of > Martin Sustrik > Sent: July 19, 2010 2:41 AM > To: 0MQ development list > Subject: Re: [zeromq-dev] "inproc" socket connection fails > onCentos5/AmazonEC > > Dmitri Toubelis wrote: > > Martin, > > > > I tried it already and if I introduce a small delay after > binding a socket, > > then everything works as supposed to. However, I bind and > then connect > > sockets sequentially from a single thread, so if these > calls are synchronous > > they should be executed in a right sequence. Is there any > "asynchronicity" > > in socket binding? If so then is there a way to disable it? > > There is no asynchronicity fro "inproc" transport. Can you > provide the > code to reproduce the problem? > > > I also noticed that socket binding on Centos5 platform > sometimes fails too. > > I will try adding another delay after socket creation and > before binding but > > this error is more rare and harder to reproduce. > > > > I also tried it on non-Amazon machine to rule out their > custom kernel, but > > result is still the same. > > The code for inproc transport is platform-agnostic. > > Martin > _______________________________________________ > zeromq-dev mailing list > zeromq-dev@lists.zeromq.org > http://lists.zeromq.org/mailman/listinfo/zeromq-dev _______________________________________________ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
