Mailing-List: contact commits-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Tue, 20 Nov 2012 07:18:58 +0000 (UTC)
From: "Lionel Cons (JIRA)" <jira@apache.org>
To: commits@activemq.apache.org
Message-ID: <1389650122.5499.1353395938833.JavaMail.jiratomcat@arcas>
In-Reply-To: <2076889276.31615.1346739307605.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (APLO-257) Better memory usage (avoid Java OOM
 exceptions)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Lionel Cons commented on APLO-257:
----------------------------------

FWIW, we tried once more with a newer snapshot (20121114-223000-129) and got the exact same behavior: several OOM exceptions:

2012-11-19 20:51:18,363 | WARN  | java.lang.OutOfMemoryError: GC overhead limit exceeded | 13b1928a88b
2012-11-19 20:51:18,364 | WARN  | DB operation failed. (entering recovery mode): java.lang.OutOfMemoryError: GC overhead limit exceeded | 13b1928a884
2012-11-19 20:51:18,364 | WARN  | DB operation failed. (entering recovery mode): java.lang.OutOfMemoryError: GC overhead limit exceeded | 13b1928a885
2012-11-19 20:51:18,364 | WARN  | java.lang.OutOfMemoryError: GC overhead limit exceeded | 13b1928a888
2012-11-19 20:51:18,363 | WARN  | java.lang.OutOfMemoryError: GC overhead limit exceeded | 13b1928a889
2012-11-19 20:51:18,363 | WARN  | java.lang.OutOfMemoryError: GC overhead limit exceeded | 13b1928a887

We would appreciate progress on this issue.
                
> Better memory usage (avoid Java OOM exceptions)
> -----------------------------------------------
>
>                 Key: APLO-257
>                 URL: https://issues.apache.org/jira/browse/APLO-257
>             Project: ActiveMQ Apollo
>          Issue Type: Improvement
>         Environment: apollo-99-trunk-20120902.143447-110
>            Reporter: Lionel Cons
>
> When running a stomp-benchmark based stress test against Apollo, it generated several OOM exceptions like:
> 2012-09-03 23:51:45,275 | WARN  | handle failed | 
> java.lang.OutOfMemoryError: Java heap space
> 2012-09-03 23:52:02,428 | WARN  |  | 
> java.lang.OutOfMemoryError: Java heap space
> 2012-09-03 23:52:01,372 | WARN  | Error for /broker | 
> java.lang.OutOfMemoryError: Java heap space
> 2012-09-03 23:51:55,554 | WARN  | Problem scavenging sessions | 
> java.lang.OutOfMemoryError: Java heap space
> The JVM already had 8GB of heap. FWIW, here are the options used: "-server -Xmx8192m -Xms4096m -XX:-UseBiasedLocking".
> Would it be possible for Apollo to detect when its getting close to the JVM limits and adjust its memory usage accordingly (reducing buffers, swapping messages to disk...)?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira