You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "Hiram Chirino (Commented) (JIRA)" <ji...@apache.org> on 2012/02/16 15:14:59 UTC
[jira] [Commented] (APLO-160) Apollo becoming unresponsive under
stress test
[ https://issues.apache.org/jira/browse/APLO-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13209377#comment-13209377 ]
Hiram Chirino commented on APLO-160:
------------------------------------
Any chance you could take heap dump? Perhaps adding the '-XX:+HeapDumpOnOutOfMemoryError' JVM option will let you take a heap dump whenyou start running out of memory. I should be able to figure out what's causing the memory pressure using that.
Also what does your stress test consist of?
> Apollo becoming unresponsive under stress test
> ----------------------------------------------
>
> Key: APLO-160
> URL: https://issues.apache.org/jira/browse/APLO-160
> Project: ActiveMQ Apollo
> Issue Type: Bug
> Environment: apollo-1.1-20120209.032648-24
> Reporter: Lionel Cons
>
> While running a stress test against apollo-1.1-20120209.032648-24 (many concurrent TCP connections), the broker became unresponsive.
> It logged several times: java.lang.OutOfMemoryError: GC overhead limit exceeded
> It also logged other warnings, probably related:
> 2012-02-14 14:14:49,273 | WARN | handle failed | org.eclipse.jetty.io.nio | Apollo Task
> 2012-02-14 14:18:39,073 | WARN | Problem scavenging sessions | org.eclipse.jetty.server.session | HashSessionScavenger-0
> It could not be stopped either, I had to kill -9 it.
> What can be done to avoid these problems?
> FWIW, java has been started with -server -Xmx8192m -Xms4096m
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira