[zeromq-dev] Sending via ROUTER socket to ROUTER socket fails initially with "No route to host"
Anoop Karollil
anoop.karollil at gmail.com
Tue Mar 26 22:55:48 CET 2013
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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: broker.py
Type: text/x-python
Size: 265 bytes
Desc: not available
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20130326/e5d0052d/attachment.py>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: client.py
Type: text/x-python
Size: 439 bytes
Desc: not available
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20130326/e5d0052d/attachment-0001.py>
More information about the zeromq-dev
mailing list