ebin123456 / py-amqplib

Automatically exported from code.google.com/p/py-amqplib
GNU Lesser General Public License v2.1
0 stars 0 forks source link

TCPTransport does not deal with framesize fragments #14

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Which version of amqplib are you using?
0.6.1

Have you checked to see if there is a newer version in the "Featured
Downloads" section of the front page of this project?
yes

Which broker are you using (RabbitMQ?) which version?
RabbitMQ 1.7.1

Which version of Python?
2.6.2

What steps will reproduce the problem?
1. Write messages > frame-max from server

What is the expected output? What do you see instead?
Connection is forcibly closed

Please provide any additional information below.
In comparison with pika, it seems amqplib is missing code to handle sending 
fragments in chunks of AMQ frame-max (minus header/footer). 

The same may also apply to the read_frame function.

Original issue reported on code.google.com by sigurd.h...@gtempaccount.com on 9 Feb 2010 at 6:04

GoogleCodeExporter commented 9 years ago
I believe amqplib does handle large messages OK, in Issue #23 we were testing 
sending 100MB messages.  In the test_channel.py unittest it sends a 160k 
message with no problem.

I think we'll need to see a more concrete example of some code that displays a 
problem before any more can be done.

Original comment by barry.pe...@gmail.com on 28 Mar 2011 at 5:35