I did not quite get the problem but could this be because (I think) router is not able to route messages to socket from which it has not reveived data first... 7.2.2014 22.51 kirjoitti "Justin Karneges" <[email protected]>:
> Hi, > > 1) ROUTER in program A is set to connect to a bind socket in program B. > 2) Both programs are started, and the connection is established. > 3) A determines B's socket identity out-of-band, and is able to send > messages to B. > 3) B is terminated and the connection is lost. > 4) B is started again, and the connection is re-established. > 5) A determines B's socket identity out-of-band, and is no longer able > to send messages to B. > > It seems this problem does not happen if B retains the same socket > identity across reconnects. However, if it uses a random identity (to be > discovered out-of-band by A), then routing will never work again after > the first restart of B. The A program must be restarted in order to make > things right again. > > My guess is that each connect queue on a ROUTER socket is somehow bound > for life against the first identity it sees. Is this intentional behavior? > > Thanks, > Justin > _______________________________________________ > zeromq-dev mailing list > [email protected] > http://lists.zeromq.org/mailman/listinfo/zeromq-dev >
_______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
