[rabbitmq-discuss] RabbitMQ Test case - Possible Memory Leak problem

Fri Jan 21 11:44:16 GMT 2011

Hi,

I've fallowed your instructions and configured my RabbitMQ server under
windows to use different configuration setup:

1) [{rabbit, [{vm_memory_high_watermark, 0.80}]}].
2) [{rabbit, [{vm_memory_high_watermark, 0.40}]}].
3) [{rabbit, [{vm_memory_high_watermark, 0.25}]}].
4) [{rabbit, [{vm_memory_high_watermark, 0.20}]}].
5) [{rabbit, [{vm_memory_high_watermark, 0.10}]}].

Every time I've started RabbiitMQ server with one of the previous
configuration and then started my Test application but every time the
RabbitMQ server crashed down after a few minutes.I don't sincerly find any
problem in my application's code and, as I've stated in previous e-mail the
test is very simple. Anyway I've attached my project and hope someone can
test my application under different machine then window because for the
moment I'm unable to operate this kind of test. Hope to have a response.
Thanks, best regards

P.S. (How to use the project):

The attached file is a MAVEN project (platform independent) which produces
as output an executable project. The project is composed by two sub-modules,
one is use to test ActiveMQ and another one is used to test RabbitMQ.
Basically the project is a ready to go for running, just configure the
properties file (server connection, login, etc.). The configuration files
are respectively placed under
"${broker_type}mq/publisher/data/publisher.properties". Both the two
sub-modules (and both publisher or subscriber applications) produces as
output a .csv file under the folder
"${broker_type}mq/${application_type}/results" where are printed some test
results. Also the messages number and the size of the message can be
configured to the publishers by using the file located under the folder
"${broker_type}mq/${application_type}/data/${broker_type}MQTesterPublisher.txt"
(an example is already provided).

Cristoforo.

2011/1/14 Matthew Sackman <matthew at rabbitmq.com>

> Hi,
>
> On Tue, Jan 11, 2011 at 12:44:54PM +0100, Crisoforo Seccia wrote:
> > . Am I adopting a very strange test case which is not well handled by
> > RabbitMQ?
>
> Not really, no. However, there are problems with RabbitMQ under Windows,
> and you may have to do some tweaking of the configuration. The fact that
> you crashed on an eheap allocation suggests that Rabbit tried to
> allocate memory that Windows refused it.
> http://www.rabbitmq.com/extensions.html#memsup
>
> Rabbit by default assumes that it's the only application running on a
> machine, and thus it can expect to be allocated all memory. You may
> wish, as suggested in the above page, to try reducing the
> vm_memory_high_watermark and repeat the tests.
>
> > . Is there any connection with the solved bug described in the RabbitMQ
> 2.2
> > release notes (“fix memory leak when long-running channels consume and
> > cancel on many queues”)?
>
> Nope - that bug would have likely taken months of constant tripping to
> actually result in any sizable memory leak.
>
> > . How does RabbitMQ handle message flooding? As stated in ActiveMQ
> official
> > page, the flow control, in the current version means that: “if the broker
> > detects that the memory limit for the destination, or the temp- or
> > file-store limits for the broker, have been exceeded, then the flow of
> > messages can be slowed down. The producer will be either blocked until
> > resources are available or will receive a JMSException”.
>
> Again, the above link will explain it all, but in short, Rabbit uses TCP
> back pressure to prevent producers flooding it with too many messages.
> Ultimately, you're always limited by the rate at which you can get rid
> of messages - whether to clients or to disk. In effect, RAM just acts as
> a huge (hopefully!) buffer.
>
> Matthew
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20110121/3099811d/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: MQTester.rar
Type: application/rar
Size: 41564 bytes
Desc: not available
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20110121/3099811d/attachment-0001.rar>