<div dir="ltr"><div>1. multicast 1.7.0.</div>Ahh.. I was looking for the multicast of 1.7.0. we only kept the (rabbit main jar).�<div><br></div><div>Ok, I ran it on the computer with the bad 2.3.1. communication and it ran it without a problem.�</div>
<div>seemed fine. I added the output (in the 1.txt file ).�</div><div><br></div><div>So,�This computer runs multicast 1.7.0 and not 2.3.1. a riddle.</div><div><br></div><div>2. Commandline�</div><div>you are right , I did �forget to add the cmdline of the bad computer. It is identical in every computer because I created a batch file and copied it to every computer.�</div>
<div><br></div><div>3. 1.7.0. to 2.3.1. -�</div><div>We decided on an emergency solution for the meanwhile - we run rabbitmq 2.3.1 server with 1.7.0. jars at the clients.</div><div>so far it seems ok. Are we expecting major problems?�</div>
<div><br></div><div>4. SQLServer port.�</div><div>We don't use it . we use my sql . I don't think it is the listening port issue - because we are connecting via Tracer.�</div><div><br></div><div>Thanks a bunch again�</div>
<div>(Open Source FTW :-) ).<br><br><div class="gmail_quote">On Wed, Mar 2, 2011 at 2:55 PM, Emile Joubert <span dir="ltr"><<a href="mailto:emile@rabbitmq.com">emile@rabbitmq.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 02/03/11 12:38, mysurf mail wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Hi,<br>
I ran the multicast main . from the computer with the good connection it<br>
seemed to work.<br>
from the computer with the bad connection - it seemed to not work.<br>
<br>
I was seconds away from taking this to the IT , but then I remembered<br>
that both computes run the RabbitMQ client 1.7.0 successfully .<br>
<br>
Maybe you can tell me what changed in the implementation of the 2.3.1 or<br>
the erlang??<br>
</blockquote>
<br></div>
The release notes should contain this information. You can get these from the rabbitmq-announce mailing list archives:<br>
<br>
<a href="http://lists.rabbitmq.com/pipermail/rabbitmq-announce/" target="_blank">http://lists.rabbitmq.com/pipermail/rabbitmq-announce/</a><br>
<br>
If version 1.7.0 worked, can you try to repeat the MulticastMain test, but using MulticastMain and client from the 1.7.0 release? You'll find it here:<br>
<br>
<a href="http://www.rabbitmq.com/releases/rabbitmq-java-client/v1.7.0/" target="_blank">http://www.rabbitmq.com/releases/rabbitmq-java-client/v1.7.0/</a><div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I am adding the output file for the multicast. it has outputs from both<br>
computers.<br>
</blockquote>
<br></div>
You have left out the full command issued on GoodComputer. Can you please supply this?<br>
<br>
You should be aware that 1434 (UDP) is a registered port for MS SQL Server. Is there any reason why you are not using the default AMQP port (5672)? Can you try using port 5672?<br>
<br>
<br>
Regards<br><font color="#888888">
<br>
Emile<br>
</font></blockquote></div><br></div></div>