Philippe Guibert

Thanks, I will use zmq_errno(). IT looks like zmq_send returned erro in req.cpp, L69. ``` // If we've sent a request and we still haven't got the reply, // we...

The issue occurs under stress conditions. The REQ-REP pattern has been followed from the beginning. And usually it works. I wanted to draw your attention to some stress condition that...

the main issue resides in the reproduction case. I tried to add some extra delay like I could see on 'lazy pirate server' on [0]. With non modified code on...

I did not see any traces showing that there was a failure on one side on an other one. I begin to think that there has been somehow some preemption...

Hi, isn't that option ZMQ_RECONNECT_IVL supposed to transparently reconnect without having to do the job at calling layer?

Hi, I was wondering about reilability. The server is supposed to send back a reply. what happens in lazy pirate client/server pattern, if server does not send the reply ?...

I mean REQ/REP pattern is simple and should be reliable on my side. but from my perspective, I see that sometimes, when REP pattern is not sent back, on the...

the pirate client pattern says to close/create socket on REQ side when a problem occurs, but somehow, the pirate server pattern example always sends back REP ( unless there is...

ci:rerun

ci:rerun core not reproduced locally.. retry