If I can not use RabbitMQ with WCF it is of no use to me...<br><br>I have run as the logtail, sendstring, addserver and the other C# based console apps samples and can not reproduce the errors that way...<br><br>I found a similar error condition occurring in this thread... <br>
<a href="http://social.msdn.microsoft.com/Forums/en-US/wcf/thread/302f159e-dec6-4ed5-aefb-54a1b95c3ac6">http://social.msdn.microsoft.com/Forums/en-US/wcf/thread/302f159e-dec6-4ed5-aefb-54a1b95c3ac6</a><br><br><snip><br>
System.Net.Sockets Verbose: 0 : [6120] Exiting Socket#35287174::Send() -> 1#1<br>System.Net.Sockets Error: 0 : [4508] Exception in the Socket#35287174::Receive - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond<br>
</snip><br><br>comments, suggestions?<br><br>thanks in advance.<br><br>re:<br><div class="gmail_quote">On Fri, Aug 14, 2009 at 6:13 AM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@lshift.net" target="_blank">matthias@lshift.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Patrick,<br>
<div><br>
Patrick Kenney wrote:<br>
> k, so I added a config file entry to disable defaultheartbeat in<br>
> ConnectionParameters.cs...<br>
><br>
> doing a subscribe no longer returns message too long error but it is<br>
> still failing...<br>
><br>
> host subscriber and host dispatcher still work...<br>
><br>
> I am attaching my trace and error files I am writing out...<br>
<br>
</div>Thanks. We are seeing the same here.<br>
<br>
In trying to track down the cause of these errors it would save us a lot<br>
of time if the code was stripped to the bare minimum:<br>
<br>
- instead of using WCF, call into the RabbitMQ .net client API directly.<br>
This eliminates a whole layer of complexity.<br>
<br>
- instead of a winforms based app, construct a command line app. This<br>
too eliminates a whole layer of complexity.<br>
<br>
- instead of reproducing the problems while running in the VS debugger,<br>
get to a point where the problem is reproducible by simply invoking a<br>
command line app from the shell.<br>
<br>
Do you think that is something you could do?<br>
<br>
<br>
Regards,<br>
<font color="#888888"><br>
Matthias.<br>
</font></blockquote></div><br>