[prev in list] [next in list] [prev in thread] [next in thread] 

List:       zeromq-dev
Subject:    Re: [zeromq-dev] Request Reply pattern
From:       Trevor Bernard <trevor.bernard () gmail ! com>
Date:       2017-05-03 20:18:09
Message-ID: CAGGWQ+KAuMsJKJ-neTTF7fEV9a3m86RTTLh45OQppt4YjeU-gQ () mail ! gmail ! com
[Download RAW message or body]

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
<RMarlborough@aaccorp.com> 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
zeromq-dev@lists.zeromq.org
https://lists.zeromq.org/mailman/listinfo/zeromq-dev
[prev in list] [next in list] [prev in thread] [next in thread]