php-ext unexpected behaviour of ZMQ_LINGER=0

[proArtex]

Issue description

Could you please verify that php-ext behaviour is incorrect according to this issue

Environment

• libzmq version 4.2.5
• ext-zmq version 1.1.3
• Mac OS Sierra 10.12.6

Minimal test code / Steps to reproduce the issue

1. create persistent context

2. create socket (PULL)

3. bind to tcp://127.0.0.1:5555

4. recv in cycle

5. create another persistent context

6. create another socket (PUSH)

7. set socket opt ZMQ_LINGER = 0

8. connect to tcp://127.0.0.1:5555

9. send message

What's the actual result? (include assertion message & call stack if applicable)

There is like 1 of 5 sent messages (step 5-9) received.

What's the expected result?

5 messages received.

[bluca]

I'm not sure I follow - what exactly is the issue? If you close a program with linger 0 then messages may be dropped

[proArtex]

PUSH socket with linger 0 stop to send messages to alive PULL one, it may send like 1 of 5 tries. PUSH socket has short fpm-script life, when PULL socket is still alive as cli.

My goal is to do not receive messages by crushed and reran PULL socket from PUSH message queue.

[bluca]

I still don't follow. You've set linger 0, and then the script exits after sending. Is that right?

[proArtex]

That's right. You can see php example here

[bluca]

That's working as intended. If you don't want messages to be lost, set linger to infinite.

[proArtex]

You didn't catch the point. I want them to be lost. But if I set linger 0 there no delivered messages at all during alive sockets.

[bluca]

Yes. That's because the script exits and the sockets are killed before the messages are delivered. That's what linger is for.

[proArtex]

Got it. Thanks!