Hi Min, Thanks for the suggestion. I added ROUTER_MANDATORY to my ROUTER but this didn't resolve my original problem however. The problem is after I reconnect on a different DEALER socket with the same identity, it no longer correctly routes the response.
I'm curious if there is a way to reuse identities upon disconnects. I'd rather not send a unique GUID with my payload since I already have my service information readily available. -Trev On Sun, Feb 24, 2013 at 9:27 PM, Min <mini...@gmail.com> wrote: > Hi, > > Please try using ROUTER_MANDATORY at router socket. If you get EHOSTUNREACH > at send, you should retry send. > > Thanks > Min > > 2013년 2월 25일 월요일에 Trevor Bernard님이 작성: >> >> Hi, >> >> I have a use case where I'd like to re-cycle DEALER identities when a >> failover situation occurs. I have one service SV1 that creates a >> DEALER connection to a ROUTER socket on SVn. SV1 has a hot standby and >> uses the same identity in a failover situation. The first connect goes >> as you would expect, but in the situation of a failover, the second >> SV1 never receives any messages from SVn. >> >> Can someone point me in the right direction on how to route back the >> response? >> >> -Trev >> _______________________________________________ >> zeromq-dev mailing list >> zeromq-dev@lists.zeromq.org >> http://lists.zeromq.org/mailman/listinfo/zeromq-dev > > > _______________________________________________ > zeromq-dev mailing list > zeromq-dev@lists.zeromq.org > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > _______________________________________________ zeromq-dev mailing list zeromq-dev@lists.zeromq.org http://lists.zeromq.org/mailman/listinfo/zeromq-dev
