<div dir="ltr">Ok,�<div>I will repeat my test results fully .�</div><div>It happens only from certain computers.�</div><div>It usually throws an exception when the command�</div><div>factory.newConnection() is invoked.�</div>
<div>the exception is ConnectionException. I have it in the initial mail of this thread.</div><div>( I can telnet that port. I can connect from other computers. I can connect to it with 1.7.0 clients )</div><div><br></div>
<div>I dont think I am acking until that point.�</div><div><br><br><div class="gmail_quote">On Tue, Mar 1, 2011 at 5:59 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 14:57, mysurf mail wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
<br>
I setup a trace at the client app server. Set the listen port and<br>
connection port and got a log for the unsuccessful<br>
factory.newConnection() . I added it in attached the tracelog.txt.<br>
</blockquote>
<br></div>
This looks like a normal trace with a successful connection establishment, and subsequent exchange and queue declarations. I would be surprised if the broker logfile contained an abrupt connection failure at the corresponding time. Can you please confirm? If possible please supply a trace of a case where an error occurs.<div class="im">
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
now regarding the other references you gave me<br>
<br>
1 Protocol errors:<br>
�Acknowledging with an unknown delivery tag<br>
�Redeclaring exchanges with different parameters<br>
<br>
you recommended not acking more than once. This whole thing started when<br>
we upgraded the rabbitmq version and Matthias sujested we will change<br>
the consumer to ack (i.e. we changed it to<br>
channel.basicConsume(queueName, FALSE, queueingConsumer);)<br>
(This is if I understood him right )<br>
So How can I control the acking . How do I know if I ack more then once.<br>
</blockquote>
<br></div>
This is more than a recommendation. From the specification:<br>
<br>
�"a client MUST not acknowledge the same message more than once."<br>
<br>
Check whether your client contains instances of "channel.basicAck". If you acknowledge messages more than once you will see a channel exception.<br><font color="#888888">
<br>
<br>
Emile<br>
</font></blockquote></div><br></div></div>