activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lionel Cons (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APLO-160) Reduce memory overhead of many connections.
Date Thu, 03 May 2012 05:34:00 GMT

    [ https://issues.apache.org/jira/browse/APLO-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13267204#comment-13267204
] 

Lionel Cons commented on APLO-160:
----------------------------------

Indeed, CPU usage was high. Fair enough to consider this a feature.
                
> Reduce memory overhead of many connections.
> -------------------------------------------
>
>                 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
>            Assignee: Hiram Chirino
>             Fix For: 1.3
>
>         Attachments: apollo.dump
>
>
> 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

        

Mime
View raw message