[zeromq-dev] Paranoid Pirate Troubles

Riskybiz riskybizlive at live.com
Fri Jun 27 12:37:58 CEST 2014


I do have a Firewall running. I am able to run the Lazy Pirate Server and
Lazy Pirate Client on the same computer and it functions as expected without
the firewall getting in the way.  Though I don't know how to test the
connection with telnet.

Riskybiz.


Message: 12
Date: Thu, 26 Jun 2014 10:52:48 -0700
From: Michel Pelletier <pelletier.michel at gmail.com>
Subject: Re: [zeromq-dev] Paranoid Pirate Troubles
To: ZeroMQ development list <zeromq-dev at lists.zeromq.org>
Message-ID:
	<CACxu=vLe+r-HvEN68ue0C9p4-Gf=-c7m87tGvB7MVrLL_EDx=Q at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Do you have a firewall running?  Can you connect to your service from any
process?  (telnet, netcat, etc...)


On Thu, Jun 26, 2014 at 10:40 AM, Riskybiz <riskybizlive at live.com> wrote:

> I?m using Visual Studio Express 2012 to build the Paranoid Pirate Pattern
> examples in Visual C++ on Windows.
>
>
>
>
>
http://zguide.zeromq.org/page:all#Robust-Reliable-Queuing-Paranoid-Pirate-Pa
ttern
>
>
>
> Downloaded the example code from GitHub https://github.com/imatix/zguide/
>
>
>
> My question is, has anyone managed to make the Paranoid Pirate Pattern in
> C++ work on Windows?  I get the following output from the components;
> ppqueue, ppworker and lpclient.  I?ve made a few minor code changes
related
> to the waiting/delay intervals to convert from seconds to milliseconds as
> Sleep() in Visual C++ requires, and also a few necessities to get the code
> to compile.  After toying around with it for quite a while I thought I?d
> ask: Anyone know how or managed to get this working??  Care to share?
>
>
>
> Thanks,
>
>
>
> Riskybiz.
>
>
>
> *ppqueue: N.B. the random symbols generated where the worker identity
> should be.*
>
> E: worker              ? not ready
>
> E: worker              ? not ready
>
> E: worker              ? not ready
>
> E: worker              ? not ready
>
> E: worker              ? not ready
>
> E: worker              ? not ready
>
> E: worker              ? not ready
>
> E: worker              ? not ready
>
> E: worker              ? not ready
>
> E: worker              ? not ready
>
> E: worker              ? not ready
>
> E: worker              ? not ready
>
> E: worker              ? not ready
>
>
>
> E: worker              ? not ready
>
> E: worker              ? not ready
>
> E: worker              ? not ready
>
> E: worker              ? not ready
>
>
>
> E: worker              ? not ready
>
> E: worker              ? not ready
>
> E: worker              ? not ready
>
> E: worker              ? not ready
>
> E: worker              ? not ready
>
>
>
> *ppworker: can never reach the queue.*
>
> I: (07EC-4F30) worker ready
>
> I: (07EC-4F30) worker heartbeat
>
> W: (07EC-4F30) heartbeat failure, can't reach queue
>
> W: (07EC-4F30) reconnecting in 1000 msec...
>
> I: (87BC-56F4) worker ready
>
> I: (87BC-56F4) worker heartbeat
>
> I: (87BC-56F4) worker heartbeat
>
> I: (87BC-56F4) worker heartbeat
>
> W: (87BC-56F4) heartbeat failure, can't reach queue
>
> W: (87BC-56F4) reconnecting in 2000 msec...
>
> I: (1320-23FE) worker ready
>
> I: (1320-23FE) worker heartbeat
>
> I: (1320-23FE) worker heartbeat
>
> I: (1320-23FE) worker heartbeat
>
> W: (1320-23FE) heartbeat failure, can't reach queue
>
> W: (1320-23FE) reconnecting in 4000 msec...
>
> I: (5894-5F2C) worker ready
>
>
>
> *lpclient: doesn?t reach the server and gives up.*
>
> I: connecting to server...
>
> W: no response from server, retrying...
>
> I: connecting to server...
>
> W: no response from server, retrying...
>
> I: connecting to server...
>
> E: server seems to be offline, abandoning





More information about the zeromq-dev mailing list