[
https://issues.apache.org/jira/browse/QPID-5786?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14126309#comment-14126309
]
Rob Godfrey edited comment on QPID-5786 at 9/9/14 12:01 AM:
------------------------------------------------------------
Hi Bobby,
Thanks a lot for the heap dump! Our apologies we've really tried to reproduce
it and not been able to - the heap dump at least gives us somewhat a clearer
picture of the nature of what you are seeing.
Do you see this failure in a number of different environments, or are you
always testing on the same (or similar) machines? If so, what are the
characteristics of that machine (memory / number of cores / etc.)
Having re-read the broker code, it's not completely clear there is a bug
per-se... this behaviour is potentially consistent with the publisher simply
sending messages faster than the consumer can consume them. In 0.30 the broker
will start to flow the messages into the message store if the queue becomes
overly large, which would potentially keep the broker alive for longer (though
if the producer keeps producing faster than the consumer consumes and there is
no limit set on the queue size, then the broker will eventually OOM). Version
0.28 and earlier will not do this and thus OOM sooner.
Can you monitor the broker through the management console while you are running
these tests? is it the case that the consumer on the queue completely stops,
or just that it consumes more slowly than the producer produces.
If the latter, what behaviour would you want of your application? If this is
the issue, you can set up flow control limits so that the broker will attempt
to stop the sender from sending when the queue gets too large (to give the
consumer a chance to catch up).
was (Author: rgodfrey):
Hi Bobby,
Thanks a lot for the heap dump! Our apologies - it does look like you've run
into some sort of bug in the Java Broker. We've really tried to reproduce it
and not been able to - the heap dump at least gives us somewhat a clearer
picture of the nature of the issue.
Do you see this failure in a number of different environments, or are you
always testing on the same (or similar) machines? If so, what are the
characteristics of that machine (memory / number of cores / etc.)
If we still can't reproduce it (and can't deduct what is happening by analysing
the code) we may need to ask you to run some tests for us with patched code
with extra debugging.
Out of interest, have you tried this test with the 0.30 (beta) code? There
have been some changes around the area where this seems to be happening which
might make a difference.
> Memory leak in qpid-java-broker-0.26.tar.gz
> -------------------------------------------
>
> Key: QPID-5786
> URL: https://issues.apache.org/jira/browse/QPID-5786
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.26
> Environment: Linux Mint 15 (64 Bit) - any Linux version should do
> Java // OpenJDK Runtime Environment (IcedTea 2.4.4)
> also tested with Java(TM) SE Runtime Environment (build 1.6.0_26-b03)
> Ruby 1.8.7
> Ruby Bunny Gem 1.2.2
> Reporter: Bobby Flitter
> Attachments: amqp_bunny_qpid.pcap
>
>
> When using the hello bunny example program from Ruby together with Apache
> qpid server the memory consumption of qpid seems to grow continuously.
> Steps to reproduce the problem in Linux:
> wget
> http://ftp-stud.hs-esslingen.de/pub/Mirrors/ftp.apache.org/dist/qpid/0.26/qpid-java-broker-0.26.tar.gz
> tar xzvf qpid-java-broker-0.26.tar.gz
> cd qpid-broker-0.26/bin/
> ./qpid-server
> - in a new terminal
> - meanwhile bunny 1.2.2. is available
> - install ruby amqp bunny
> sudo gem install bunny
> - download hello bunny example
> wget http://pastebin.com/raw.php?i=f6MesMCZ -O hello_bunny.rb
> while true; do ruby hello_bunny.rb ; done
> - in another terminal:
> while true; do grep "^VmRSS" /proc/$(pgrep -f qpid)/status ; sleep 1;done
> - memory consumption of java qpid is growing continuously until
> OutOfMemoryError ends the server
> Unhandled Exception java.lang.OutOfMemoryError: Java heap space in Thread
> Thread-1
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
