Hi Ian, No, without the load balancer in the picture, when I start the worker, and then start the client, using the port the worker is listening (5560), the client sends messages (multipart) and gets back the response as intended. Then I start the balancer executable, which has 5559 for front end end 5560 for back end. When I make the client send messages to 5559 (where the load balancer is listening) the code begins to wait for the first message's response, and it never receives it. a summary of config:
client (connects to 5559) <---> Balancer (front end:5559 back end:5560 ) <----> worker(binds to:5560) This is windows xp with sp3, latest 2.1 code from git Thanks for your response Seref On Mon, Jun 6, 2011 at 3:13 PM, Ian Barber <[email protected]> wrote: > > On Mon, Jun 6, 2011 at 3:01 PM, Seref Arikan > <[email protected]> wrote: >> >> With three executables: client, load balancer and worker process, what >> is the order of execution I need? Am I missing a point go get this >> working? > > Shouldn't matter - I presume you are calling bind() on the two ports on the > load balancer and connect on the client and worker? In that case the work > and client should just try to reconnect until the load balancer appears. > When you say client and worker processes can connect succesfully, do you > mean that if you start the load balancer first they both connect > succesfully? > > Ian > > > _______________________________________________ > 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
