I'm using zmq 3.2.2 stable GCC 4.4.6 20120305 (Red Hat 4.4.6-4) x86_64 CentOS 6.3 2.6.32-279.14.1.el6.x86_64
Regards, Cheyi On Mon, Dec 10, 2012 at 3:36 PM, CheYi Lin <[email protected]> wrote: > Hi, > > I'm doing some zmq ROUTER-to-ROUTER experiments in my distributed > system prototype. > (single threaded, libev event loop based application) > > Below is my test steps: > > 1. ROUTER A and B start, set unique identity, bind the address. > > (handshake) > 2. A connect to B. > 3. A send HELLO to B continuously. > 4. B recv HELLO then send HELLO_ACK back to A. > 5. A recv HELLO_ACK and stop sending HELLO, handshake finished. > > (start communication) > 6. A and B send HEARTBEAT to each other every 0.5 seconds. > 7. When HEARTBEAT received, A and B print "recv HEARTBEAT". > > After about 30 seconds, A stop printing "recv HEARTBEAT" but B > continue printing "recv HEARTBEAT". > And few seconds later I terminate B, suddenly A print lots of "recv > HEARTBEAT". > > I notice that A stop being signaled from the ZMQ_FD (in gdb), so all > HEARTBEAT from B was queued > after A stop printing "recv HEARTBEAT". > > My zmq-event handler: > http://pastebin.com/6JiSh46N > > Don't know why the handler stop receiving ZMQ_EVENTS events. > Could someone please review my code and give me some suggestions? > > Sorry for my bad english. > > > Regards, > Cheyi _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
