[zeromq-dev] zmq errno 156384763

[Rakesh Patel]

Hi Pieter,

Yes, it is easily reproducible in following steps.

1) Sever creates "ZMQ_REP" socket and bind it to  "tcp://*:5555" and blocks
on zmq_recv.
2) Client creates "ZMQ_REQ" socket and connect it to "tcp://localhost:5555".
3) Client send "hello" message and waits for Sever response.
4) Sever receive "hello" message, Server reply with two messages
(multi-part messages). First message "Fine" and send_more to true. Second
message "ZERO length message" and send_more to false.
5) Client receives first "FINE" message on first zmq_recv and failed with
zmq errno 156384763 on second zmq_recv.

Why zmq_send not able to send "zero length message" ?

Thank you,

--Rakesh

Message: 3
Date: Wed, 27 Feb 2013 19:19:27 +0100
From: Pieter Hintjens <ph at imatix.com>
Subject: Re: [zeromq-dev] zmq errno 156384763
To: ZeroMQ development list <zeromq-dev at lists.zeromq.org>
Message-ID:
        <CADL5_si386wLUmRv-=
NjHMXeQ3UknORa-ar7d=pQY4qe8C5DKw at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1

Hi Rakesh,

Can you reproduce this with a minimal test case?

-Pieter

On Wed, Feb 27, 2013 at 6:01 PM, Rakesh Patel
<rakesh.patel8552 at gmail.com> wrote:
> Hi ,
>
> I am trying to send multi-part messages using zmq_send function. In the
last
> message, i set send_more to zero and this is zero sized message. On the
> receiving end using zmq_recv, it sets zmq errno 156384763 when receiving
> last message. In the documentation, it has written "You may send
zero-length
> messages, e.g. for sending a signal from one thread to another." then why
it
> is giving error.
>
> Is it going to cause any issue (memory leak ?? or any) ?
>
> Please let me know,
>
> Thank you,
>
> --Rakesh
>
>
> _______________________________________________
> 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/20130228/8660ad02/attachment.htm>