[
https://issues.apache.org/jira/browse/QPID-6332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14286461#comment-14286461
]
Mark Soderquist edited comment on QPID-6332 at 1/21/15 10:48 PM:
-----------------------------------------------------------------
After some more testing I have come to believe that this is due to high GC load
when there are enough messages to cause an OutOfMemoryError. I suggest this is
related to QPID-6331. My reasoning is that I increased the JVM memory from
2048m to 4096m after causing the OutOf MemoryError, so that I could get my
server to start, and it started quickly (just seconds) again.
was (Author: m...@soderquist.net):
After some more testing I have come to believe that this is due to high GC load
when there are enough messages to cause an OutOfMemoryError. I suggest this is
related to QPID-6331.
> Broker start slow when there are a lot of messages
> --------------------------------------------------
>
> Key: QPID-6332
> URL: https://issues.apache.org/jira/browse/QPID-6332
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Affects Versions: 0.30
> Environment: Red Hat Linux 6.5
> java version "1.7.0_71"
> OpenJDK Runtime Environment (rhel-2.5.3.1.el6-x86_64 u71-b14)
> OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode)
> Reporter: Mark Soderquist
>
> When there are a lot of messages in a queue it can take a long time (20+
> minutes) for the broker to start. We have a queue with 50,000+ 5KB messages
> in it that appears to cause the broker to take a long time to start. Once the
> messages are removed from the queue the broker restart only takes seconds
> again.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
