ace-commits mailing list archives

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

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

Marcel Offermans commented on ACE-517:
--------------------------------------

Ah, that's the part I missed in your initial description, you're invoking the resolver from
the Web UI.

We embed the Felix resolver, and invoke it with the bundles that are associated with the target
plus the "initial environment" (which is that big text in the UI). Then we ask the resolver
if this combination works. For some reason that runs out of memory.

We should at least catch that case, and report back to the user.

We should also investigate if an update to the resolver fixes this issue. I am pretty sure
we are currently not using the latest resolver from Felix.

> java.lang.OutOfMemoryError: GC overhead limit exceeded
> ------------------------------------------------------
>
>                 Key: ACE-517
>                 URL: https://issues.apache.org/jira/browse/ACE-517
>             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
(v6.3.4#6332)

Mime
View raw message