<div dir="ltr">Hi, <div><br></div><div><br></div><div>I setup a trace at the client app server. Set the listen port and connection port and got a log for the unsuccessful factory.newConnection() . I added it in attached the tracelog.txt.</div>
<div><br></div><div>now regarding the other references you gave me </div><div><br></div><div>1 Protocol errors:<br> Acknowledging with an unknown delivery tag<br> Redeclaring exchanges with different parameters<br></div><div>
<br></div><div>you recommended not acking more than once. This whole thing started when we upgraded the rabbitmq version and Matthias sujested we will change the consumer to ack (i.e. we changed it to <span class="Apple-style-span" style="border-collapse: collapse; color: rgb(80, 0, 80); font-family: arial, sans-serif; font-size: 13px; ">channel.basicConsume(</span><span class="Apple-style-span" style="border-collapse: collapse; color: rgb(80, 0, 80); font-family: arial, sans-serif; font-size: 13px; "></span><span class="Apple-style-span" style="border-collapse: collapse; color: rgb(80, 0, 80); font-family: arial, sans-serif; font-size: 13px; ">queueName, FALSE, queueingConsumer);</span>) </div>
<div>(This is if I understood him right )</div><div>So How can I control the acking . How do I know if I ack more then once. I think I never send an ack consciously. only through the subscibe . </div><div><br></div><div>I hope the second and the third will be solved with the trace. </div>
<div><br></div><div><div style="direction: ltr;">and thanks again. </div><br><div class="gmail_quote">On Tue, Mar 1, 2011 at 3:41 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;">Hi,<div class="im"><br>
<br>
On 01/03/11 12:55, mysurf mail wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Emile,<br>
I have a few questions:<br>
1. On the rabbitmq server we have a few Erlang versions. Should that<br>
create a problem .<br>
</blockquote>
<br></div>
Keep in mind that different features of RabbitMQ have different minimum requirements (e.g. SSL and some plugins). This is especially important in a multi-version environment. It is best to use the latest version across the board if possible (unless it is an alpha version containing an A).<div class="im">
</div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
(For now, I finished removing the older ones, so currently we have only<br>
5.8.2 and the problem still exists<br>
2. I have added the logs file from the rabbitmq server. I am the ip that<br>
ends with 170.120 and my last trial had an exception.<br>
</blockquote>
<br></div>
It is unusual to have the broker listen on port 1434. From the log there are at least 3 kinds of problems:<br>
<br>
1 Protocol errors:<br>
Acknowledging with an unknown delivery tag<br>
Redeclaring exchanges with different parameters<br>
These will lead to a channel or connection closure.<br>
<br>
2 1-Mar-2011::14:15:02<br>
Handshake timeout<br>
This will close the connection<br>
<br>
3 1-Mar-2011::14:18:46<br>
Abrupt connection termination<br>
<br>
The first can be solved by making sure that you don't acknowledge messages more than once, and that you declare exchanges with identical parameters. The second and third may have a related root cause, which the tracer or network diagnostic tools should help to identify.<div class="im">
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
3. Now about that tracer. I have been having some hard time finding<br>
documentation for it.<br>
Should I run it from the client (it comes with the client packacge) or<br>
in the server? I am running it in the client.<br>
my rabbit node port is 1434. so I am running it with<br>
.\runjava.bat co m.rabbitmq.tools.Tracer 1434 192.168.100.251 5672<br>
are my parameters ok ?<br>
</blockquote>
<br></div>
See <a href="http://www.rabbitmq.com/examples.html#tracer" target="_blank">http://www.rabbitmq.com/examples.html#tracer</a> .<br>
Judging by your logfile you want to use 1434 as the connectPort argument instead of 5672.<div class="im"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I used rabbit node port as listenport and 5672 as connect port. I also<br>
switched them but no luck . I didnt see anything on the cmd when I<br>
invoked my produce command.<br>
here it is<br>
</blockquote>
<br></div>
You should configure AMQP clients to connect to the tracer instead of to the broker directly. The port should be the one given as the first argument (listenPort) and the host should be the IP number of the machine running the tracer.<br>
<font color="#888888">
<br>
<br>
<br>
<br>
-Emile<br>
</font></blockquote></div><br></div></div>