[zeromq-dev] Sending via ROUTER socket to ROUTER socket fails initially with "No route to host"

A. Mark gougolith at gmail.com
Wed Mar 27 02:11:16 CET 2013

I see, so since it's unrestricted it's fine with ROUTER to ROUTER, but with
REQ-ROUTER is not going to work.

On Tue, Mar 26, 2013 at 2:55 PM, Anoop Karollil <anoop.karollil at gmail.com>wrote:

> Pieter Hintjens wrote:
>> On Tue, Mar 26, 2013 at 10:09 PM, Anoop Karollil
>> <anoop.karollil at gmail.com> wrote:
>>  And
>>> yes, like you said, the send after connect succeeds if there is a pause
>>> in
>>> between.
>> The send should work immediately after connect, which creates a pipe
>> at once. It's the bind that's troublesome.
> I do see the send after connect failing if it is done immediately after,
> and it succeeding if there is a pause in between.
> Please see the example python programs. Starting the broker first (which
> binds and does a receive), and then the client after (which connects and
> sends), results in the client send failing, unless there is a pause after
> the connect.
> If you uncomment the sleep in client.py, it works without failure. If you
> don't, it will fail for a while and then succeed.
> Thanks,
> Anoop
> _______________________________________________
> 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/20130326/38372b7d/attachment.htm>

More information about the zeromq-dev mailing list