ace-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Offermans (JIRA)" <>
Subject [jira] [Commented] (ACE-517) java.lang.OutOfMemoryError: GC overhead limit exceeded
Date Thu, 21 May 2015 06:01:13 GMT


Marcel Offermans commented on ACE-517:

Just to be sure, with the "Apache ACE Web Admin" you mean the Web UI? And with "displaying
bundle wiring" you mean looking at the bundles, and their association to features, distributions
and targets?

To answer your question, ACE does not load all bundles into memory, but it does load all the
metadata into memory so if you have a really big list of bundles inside the ACE repository
you might run out of memory. What kind of memory settings are you using right now? And are
you using the "all in one" server (that includes the Web UI) or are you running the server
and client as separate processes?

We need more information to establish if you ran into some memory leak or some other bug we
should fix.

> java.lang.OutOfMemoryError: GC overhead limit exceeded
> ------------------------------------------------------
>                 Key: ACE-517
>                 URL:
>             Project: ACE
>          Issue Type: Bug
>          Components: Deployment
>    Affects Versions: 2.0.1
>         Environment: centos
>            Reporter: Ali Raza
> After deploying bundles using Apache ACE Command line client when i verify deployment
using Apache ACE Web Admin. It does not show the pop displaying bundle wiring. Instead server
console displays the following error: 
> Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded
> As per my experience it could be because the bundle repository has grown and Apache Ace
perhaps loads all the bundles into memory. Well I am not sure about that. I will thankful
if someone could help in resolving this problem.

This message was sent by Atlassian JIRA

View raw message