Return-Path: X-Original-To: apmail-ace-commits-archive@www.apache.org Delivered-To: apmail-ace-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C939417DF6 for ; Tue, 19 May 2015 08:30:04 +0000 (UTC) Received: (qmail 14754 invoked by uid 500); 19 May 2015 08:30:04 -0000 Delivered-To: apmail-ace-commits-archive@ace.apache.org Received: (qmail 14715 invoked by uid 500); 19 May 2015 08:30:04 -0000 Mailing-List: contact commits-help@ace.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ace.apache.org Delivered-To: mailing list commits@ace.apache.org Received: (qmail 14295 invoked by uid 99); 19 May 2015 08:30:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 May 2015 08:30:04 +0000 Date: Tue, 19 May 2015 08:30:04 +0000 (UTC) From: "Ali Raza (JIRA)" To: commits@ace.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (ACE-517) java.lang.OutOfMemoryError: GC overhead limit exceeded MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Ali Raza created ACE-517: ---------------------------- Summary: 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)