M3 C++ broker with the "--auth no" option did the job. I'll worry about the authentication failure problem later. Thanks Gordon/Robert for your help.
Kamran Saadatjoo -----Original Message----- From: Gordon Sim [mailto:[EMAIL PROTECTED] Sent: Monday, May 12, 2008 8:19 AM To: [email protected] Subject: Re: Communication problem between M3 Broker and AMQP client Kamran Saadatjoo wrote: > It turns out that this is a firewall problem after all. I though I had > disabled the firewall on the Linux machine, but I guess I had not. I > attempted to disable the firewall again, and now I'm getting further. I see > the connection traced on the broker side, but the client is hanging > indefinitely on the connect statement. Thats most likely an authentication failure that the client isn't handling. (I could confirm if you send the broker trace). The simplest thing initially is to turn of authentication for the broker: pass in --auth no when starting it up and try again. Internal Virus Database is out-of-date. Checked by AVG. Version: 7.5.519 / Virus Database: 269.22.13/1375 - Release Date: 4/12/2008 11:32 AM Internal Virus Database is out-of-date. Checked by AVG. Version: 7.5.519 / Virus Database: 269.22.13/1375 - Release Date: 4/12/2008 11:32 AM
