Re: [zeromq-dev] Lost message with PUSH/PULL

So it is a confirmed bug, solving it might be complicated. I will take a look tomorrow. On Fri, Jul 1, 2016 at 5:53 PM, KIU Shueng Chuan wrote: > I have attached some minimal code here where doing a TCP connect to > the PUSH bind socket makes the latter writable. > > Tested

Re: [zeromq-dev] Lost message with PUSH/PULL

I have attached some minimal code here where doing a TCP connect to the PUSH bind socket makes the latter writable. Tested on 4.1.4 On 30 June 2016 at 23:11, Doron Somech wrote: > I think it might be the ZeroMQ behavior (which is probably a bug), once the > connection is

Re: [zeromq-dev] Lost message with PUSH/PULL

I think it might be the ZeroMQ behavior (which is probably a bug), once the connection is open ZeroMQ start to queue messages for the connection, even if handshake is not yet completed, so when you do telnet the message is not discarded but queue for the telnet connection. I think only PUSH is

Re: [zeromq-dev] Lost message with PUSH/PULL

The latest API documentation does suggest that messages are NOT discarded. It would probably help everybody if you could provide the code (or at least recreate your problem with a simpler example). Creating a simple example might even lead you to discover what is going wrong. So it is definitely

[zeromq-dev] Lost message with PUSH/PULL

Hi every guys: I got a problem which ZMQ will lost some messages with PUSH/PULL ZMQ socket. The scene like this: A: PUSH socket, bind address "tcp://*.1209" B: PULL socket, connect to "tcp://localhost:1209" Run the command "telnet localhost 1209" while A