It's a long-standing bug that is very difficult to fix. The work around is to
do as you discovered which is *always bind first* and then connect when using
inproc transport.
For details as to why this is hard, try searching the mailing list archive. The
answer would have been given by Martin Sustrik. You can also check the bug
database for a write-up on this.
cr
On Oct 18, 2012, at 11:55 AM, Kah-Chan Low wrote:
> Hi,
> When I do this I will get a "connection refused" error:
>
> socket1.connect("inproc://abc");
> socket2.bind("inproc://abc");
>
> When I reverse the order of the statements everything works fine.
> Both sockets have been created with the same ZMQ context.
>
> Is this a feature or a bug?
>
> Thanks!
> KC
>
>
> _______________________________________________
> 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
