activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lionel Cons (JIRA)" <>
Subject [jira] [Commented] (APLO-160) Apollo becoming unresponsive when stressed with 48k connections.
Date Wed, 02 May 2012 07:29:02 GMT


Lionel Cons commented on APLO-160:

I've made some tests and indeed Apollo behaves now slightly better with the default settings.
I've seen around 15% less memory used compared to a one month old snapshot However, I still
see a large number of connection timed out (~50).

I've also tried with reduced buffers (4k at TCP and STOMP level) and the results are much
better. Memory usage dropped a lot as well as the number of connection timed out (6). Would
it be possible to further reduce the number of connection timed out by giving yet more priority
to new connection handling?

FWIW, with the default settings, Apollo seems to take 370kB of RAM per producer. With 4k buffers,
this goes down to 120kB. Auto-tuning (APLO-163) would really be great ;-)
> Apollo becoming unresponsive when stressed with 48k connections.
> ----------------------------------------------------------------
>                 Key: APLO-160
>                 URL:
>             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 | | 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:!default.jspa
For more information on JIRA, see:


View raw message