[rabbitmq-discuss] Fwd: socket error while using rabbitmq and a NAT (Network address translation)

Wed Mar 2 13:25:23 GMT 2011

1. multicast 1.7.0.
Ahh.. I was looking for the multicast of 1.7.0. we only kept the (rabbit
main jar).

Ok, I ran it on the computer with the bad 2.3.1. communication and it ran it
without a problem.
seemed fine. I added the output (in the 1.txt file ).

So, This computer runs multicast 1.7.0 and not 2.3.1. a riddle.

2. Commandline
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.

3. 1.7.0. to 2.3.1. -
We decided on an emergency solution for the meanwhile - we run rabbitmq
2.3.1 server with 1.7.0. jars at the clients.
so far it seems ok. Are we expecting major problems?

4. SQLServer port.
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.

Thanks a bunch again
(Open Source FTW :-) ).

On Wed, Mar 2, 2011 at 2:55 PM, Emile Joubert <emile at rabbitmq.com> wrote:

> On 02/03/11 12:38, mysurf mail wrote:
>
>>
>> Hi,
>> I ran the multicast main . from the computer with the good connection it
>> seemed to work.
>> from the computer with the bad connection - it seemed to not work.
>>
>> I was seconds away from taking this to the IT , but then I remembered
>> that both computes run the RabbitMQ client 1.7.0 successfully .
>>
>> Maybe you can tell me what changed in the implementation of the 2.3.1 or
>> the erlang??
>>
>
> The release notes should contain this information. You can get these from
> the rabbitmq-announce mailing list archives:
>
> http://lists.rabbitmq.com/pipermail/rabbitmq-announce/
>
> 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:
>
> http://www.rabbitmq.com/releases/rabbitmq-java-client/v1.7.0/
>
>
>  I am adding the output file for the multicast. it has outputs from both
>> computers.
>>
>
> You have left out the full command issued on GoodComputer. Can you please
> supply this?
>
> 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?
>
>
> Regards
>
> Emile
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20110302/619962d4/attachment-0001.htm>
-------------- next part --------------
runjava com.rabbitmq.examples.MulticastMain -h 192.168.100.251 -p 1434  -e X1X1X1X1
starting consumer #0
starting producer #0
recving rate: 9181 msg/s, min/avg/max latency: 649/4119/21416 microseconds
sending rate: 10593 msg/s
recving rate: 11542 msg/s, min/avg/max latency: 684/4411/23102 microseconds
sending rate: 11622 msg/s
recving rate: 11485 msg/s, min/avg/max latency: 658/4310/22290 microseconds
sending rate: 11420 msg/s
recving rate: 11837 msg/s, min/avg/max latency: 683/4080/13151 microseconds
sending rate: 11761 msg/s
recving rate: 11328 msg/s, min/avg/max latency: 638/4442/27193 microseconds
sending rate: 11456 msg/s
recving rate: 7744 msg/s, min/avg/max latency: 691/16374/364184 microseconds
sending rate: 6152 msg/s
recving rate: 9992 msg/s, min/avg/max latency: 660/7694/537484 microseconds
sending rate: 11760 msg/s
recving rate: 11754 msg/s, min/avg/max latency: 663/4186/28967 microseconds
sending rate: 11882 msg/s
recving rate: 11863 msg/s, min/avg/max latency: 617/3938/17927 microseconds
sending rate: 11946 msg/s
recving rate: 11782 msg/s, min/avg/max latency: 610/4699/22992 microseconds
sending rate: 11900 msg/s