[rabbitmq-discuss] Trying to do a simple subscription returns message too long error... (RabbitMq.Net)

[Alexis Richardson]

On Fri, Aug 14, 2009 at 4:47 PM, Patrick Kenney<pekenney at gmail.com> wrote:
> If I can not use RabbitMQ with WCF it is of no use to me...

Patrick, we want you to be able to use RabbitMQ with WCF but need your
help isolating the bug.  I know this is a bore.

alexis



> I have run as the logtail, sendstring, addserver and the other C# based
> console apps samples and can not reproduce the errors that way...
>
> I found a similar error condition occurring in this thread...
> http://social.msdn.microsoft.com/Forums/en-US/wcf/thread/302f159e-dec6-4ed5-aefb-54a1b95c3ac6
>
> <snip>
> System.Net.Sockets Verbose: 0 : [6120] Exiting Socket#35287174::Send()
> -> 1#1
> 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
> </snip>
>
> comments, suggestions?
>
> thanks in advance.
>
> re:
> On Fri, Aug 14, 2009 at 6:13 AM, Matthias Radestock <matthias at lshift.net>
> wrote:
>>
>> Patrick,
>>
>> Patrick Kenney wrote:
>> > k, so I added a config file entry to disable defaultheartbeat in
>> > ConnectionParameters.cs...
>> >
>> > doing a subscribe no longer returns message too long error but it is
>> > still failing...
>> >
>> > host subscriber and host dispatcher still work...
>> >
>> > I am attaching my trace and error files I am writing out...
>>
>> Thanks. We are seeing the same here.
>>
>> In trying to track down the cause of these errors it would save us a lot
>> of time if the code was stripped to the bare minimum:
>>
>> - instead of using WCF, call into the RabbitMQ .net client API directly.
>> This eliminates a whole layer of complexity.
>>
>> - instead of a winforms based app, construct a command line app. This
>> too eliminates a whole layer of complexity.
>>
>> - instead of reproducing the problems while running in the VS debugger,
>> get to a point where the problem is reproducible by simply invoking a
>> command line app from the shell.
>>
>> Do you think that is something you could do?
>>
>>
>> Regards,
>>
>> Matthias.
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>