[rabbitmq-discuss] Large Message Timeout on Receive

Fri May 28 17:56:50 BST 2010

Sure, the server version is 1.7.2 and the .NET API Dll is 1.7.2 too.

Thanks.

Ryan Teising
1 Bryant Park
9th Floor, 09N-221
New York, NY 10036
Office: 646-855-2611
Mobile: 201-710-0718

-----Original Message-----
From: rabbitmq-discuss-bounces at lists.rabbitmq.com
[mailto:rabbitmq-discuss-bounces at lists.rabbitmq.com] On Behalf Of Simon
MacMullen
Sent: Friday, May 28, 2010 12:28 PM
To: rabbitmq-discuss at lists.rabbitmq.com
Subject: Re: [rabbitmq-discuss] Large Message Timeout on Receive

Hi Ryan.

There certainly should not be a problem with messages of that size. I 
don't have a .NET development environment to hand right now but as a 
sanity check I converted your test program into Python and it worked 
fine (against 1.7.2).

I'll poke about in the .NET client next week - in the meantime can you 
confirm the client and server versions you're using?

Cheers, Simon

On 28/05/10 16:26, Teising, Ryan (FICC Principal Technology) wrote:
> I put together the attached sample code (using the .NET API).
>
> <<Program.cs>>
> I put 10 messages on a queue, and then I try to read those same
messages
> off of the queue.
>
> The first call to BasicGet returns the first message, but the second
> call to BasicGet never returns. If I reduce the size of the of the
> messages down to 4096 bytes (instead of 2097152), then the BasicGet
> calls work as expected.
>
> Is there a size limitation on on messages that can be put on the
queue?
>
> /Ryan Teising/
> /1 Bryant Park/
> /9th Floor, 09N-221/
> /New York, NY 10036/
> /Office: 646-855-2611/
> /Mobile: 201-710-0718/
>
>
------------------------------------------------------------------------
> This message w/attachments (message) may be privileged, confidential
or
> proprietary, and if you are not an intended recipient, please notify
the
> sender, do not use or share it and delete it. The information
contained
> in this e-mail was obtained from sources believed to be reliable;
> however, the accuracy or completeness of this information is not
> guaranteed. Unless specifically indicated, this message is not an
offer
> to sell or a solicitation of any investment products or other
financial
> product or service, an official confirmation of any transaction, or an
> official statement of Merrill Lynch. Subject to applicable law,
Merrill
> Lynch may monitor, review and retain e-communications (EC) traveling
> through its networks/systems. The laws of the country of each
> sender/recipient may impact the handling of EC, and EC may be
archived,
> supervised and produced in countries other than the country in which
you
> are located. This message cannot be guaranteed to be secure or
> error-free. References to "Merrill Lynch" are references to any
company
> in the Merrill Lynch & Co., Inc. group of companies, which are
> wholly-owned by Bank of America Corporation. Securities and Insurance
> Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose
> Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking
> Service or Activity * Are Not Insured by Any Federal Government
Agency.
> Past performance is no guarantee of future results. Attachments that
are
> part of this E-communication may have additional important disclosures
> and disclaimers, which you should read. This message is subject to
terms
> available at the following link:
> http://www.ml.com/e-communications_terms/. By messaging with Merrill
> Lynch you consent to the foregoing.
>
------------------------------------------------------------------------
>
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

_______________________________________________
rabbitmq-discuss mailing list
rabbitmq-discuss at lists.rabbitmq.com
http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

--------------------------------------------------------------------------
This message w/attachments (message) may be privileged, confidential or proprietary, and if you are not an intended recipient, please notify the sender, do not use or share it and delete it. The information contained in this e-mail was obtained from sources believed to be reliable; however, the accuracy or completeness of this information is not guaranteed. Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Merrill Lynch. Subject to applicable law, Merrill Lynch may monitor, review and retain e-communications (EC) traveling through its networks/systems. The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or error-free. References to "Merrill Lynch" are references to any company in the Merrill Lynch & Co., Inc. group of companies, which are wholly-owned by Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Past performance is no guarantee of future results. Attachments that are part of this E-communication may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: http://www.ml.com/e-communications_terms/. By messaging with Merrill Lynch you consent to the foregoing.
--------------------------------------------------------------------------