[rabbitmq-discuss] MulticastMain Java client causes Erlang error eheap_alloc: Cannot allocate 467078560 bytes of memory (of type "heap") (with RabbitMQ 1.7.1)

John Apps johndapps at gmail.com
Tue Jan 26 18:32:51 GMT 2010


Here are two runs, one with 0.4 and the other, below, with 0.3. Both crash.
The rabbit.log for the 0.3 test is attached. The 0.4 test did not log any
memory watermark messages, only the 0.3 test.
The page file on this machine is 8GB with a maximum size of 16GB.
_________________________________________________
The client:
here we go at 19:16:49.49 2010-01-26
starting consumer #0
starting producer #0
sending rate: 11280 msg/s
sending rate: 10228 msg/s
sending rate: 10017 msg/s
sending rate: 10069 msg/s
sending rate: 9613 msg/s
...
...Crash
...
The server with 0.4 memory:
eheap_alloc: Cannot allocate 298930300 bytes of memory (of type "heap").
=INFO REPORT==== 26-Jan-2010::19:16:46 ===
Memory limit set to 1634MB.

=INFO REPORT==== 26-Jan-2010::19:16:46 ===
disk_log: repairing
"c:/AMQP/RabbitMQ/rabbitmq_server-1.7.1/db/BIGPOOH-mnesia/rabbit_persister.LOG"
...

=INFO REPORT==== 26-Jan-2010::19:16:46 ===
Repaired persister log - 1 recovered, 0 bad

=INFO REPORT==== 26-Jan-2010::19:16:46 ===
Rolling persister log to
"c:/AMQP/RabbitMQ/rabbitmq_server-1.7.1/db/BIGPOOH-mnesia/rabbit_persister.LOG.previous"

=INFO REPORT==== 26-Jan-2010::19:16:46 ===
started TCP Listener on 0.0.0.0:5672

=INFO REPORT==== 26-Jan-2010::19:16:49 ===
accepted TCP connection on 0.0.0.0:5672 from 127.0.0.1:42109

=INFO REPORT==== 26-Jan-2010::19:16:49 ===
starting TCP connection <0.143.0> from 127.0.0.1:42109

=INFO REPORT==== 26-Jan-2010::19:16:49 ===
accepted TCP connection on 0.0.0.0:5672 from 127.0.0.1:42110

=INFO REPORT==== 26-Jan-2010::19:16:49 ===
starting TCP connection <0.149.0> from 127.0.0.1:42110
______________________________________________________________
This is with 0.3 memory:
=INFO REPORT==== 26-Jan-2010::19:22:09 ===
Memory limit set to 1225MB.

=INFO REPORT==== 26-Jan-2010::19:22:09 ===
disk_log: repairing
"c:/AMQP/RabbitMQ/rabbitmq_server-1.7.1/db/BIGPOOH-mnesia/rabbit_persister.LOG"
...

=INFO REPORT==== 26-Jan-2010::19:22:09 ===
Repaired persister log - 1 recovered, 0 bad

=INFO REPORT==== 26-Jan-2010::19:22:09 ===
Rolling persister log to
"c:/AMQP/RabbitMQ/rabbitmq_server-1.7.1/db/BIGPOOH-mnesia/rabbit_persister.LOG.previous"

=INFO REPORT==== 26-Jan-2010::19:22:10 ===
started TCP Listener on 0.0.0.0:5672

=INFO REPORT==== 26-Jan-2010::19:22:13 ===
accepted TCP connection on 0.0.0.0:5672 from 127.0.0.1:42320

=INFO REPORT==== 26-Jan-2010::19:22:13 ===
starting TCP connection <0.143.0> from 127.0.0.1:42320

=INFO REPORT==== 26-Jan-2010::19:22:13 ===
accepted TCP connection on 0.0.0.0:5672 from 127.0.0.1:42321

=INFO REPORT==== 26-Jan-2010::19:22:13 ===
starting TCP connection <0.149.0> from 127.0.0.1:42321

___________________________________________________
here we go at 19:25:50.62 2010-01-26
starting consumer #0
starting producer #0
sending rate: 11216 msg/s
sending rate: 11214 msg/s
sending rate: 10332 msg/s
sending rate: 9481 msg/s
sending rate: 7449 msg/s
sending rate: 6095 msg/s
sending rate: 3217 msg/s
sending rate: 998 msg/s
...
...crash
...
temp_alloc: Cannot allocate 197209248 bytes of memory (of type "tmp_heap").

Log file is attached.

________________________
*>>>That's exactly what is supposed to happen. Rabbit has told the producer
to stop sending messages since it is under memory pressure. Once memory
becomes available again, e.g. when a consumer consumes enough messages, or
some queues get deleted/purged, or as a result of internal garbage
collection, Rabbit will tell the producer that it may resume.
*

The funny thing is that rabbitmqctl status returned a 'node down' message. I
suppose that is OK?
_______________

Cheers, John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20100126/0225ebf1/attachment.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: BIGPOOH.log
Type: application/octet-stream
Size: 4995 bytes
Desc: not available
Url : http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20100126/0225ebf1/attachment.obj 


More information about the rabbitmq-discuss mailing list