[zeromq-dev] inproc: need to bind to an address before connect?

Chuck Remes lists at chuckremes.com
Thu Oct 18 18:57:18 CEST 2012

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.


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 at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20121018/407361fb/attachment.htm>

More information about the zeromq-dev mailing list