REQ/REP happens in lockstep aka ping then pong -- the assertion happens by design. You'll have to create a new REP socket as well. IMHO the REQ/REP pattern has very limited use in real world applications. I suggest taking a look at ROUTER/DEALER instead.
On Wed, May 3, 2017 at 3:00 PM, Marlborough, Rick <[email protected]> wrote: > Designation: Non-Export Controlled Content > > Folks; > > We have test software that is testing the request reply > pattern. We are doing failure testing. The failure testing involves killing > and restarting the server. We have code in the requester that “attempts” to > do a reconnect to the server. However, after the reconnect, the subsequent > send calls always fail and ZeroMQ reports “Operation cannot be accomplished > in current state”. Is there a way to “reset” a request socket and clear this > condition? > > > > Thanks > > Rick _______________________________________________ zeromq-dev mailing list [email protected] https://lists.zeromq.org/mailman/listinfo/zeromq-dev
