Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 52570200C92 for ; Mon, 12 Jun 2017 17:50:05 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 5109F160BDE; Mon, 12 Jun 2017 15:50:05 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id A016C160BD6 for ; Mon, 12 Jun 2017 17:50:04 +0200 (CEST) Received: (qmail 55514 invoked by uid 500); 12 Jun 2017 15:50:03 -0000 Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@karaf.apache.org Delivered-To: mailing list issues@karaf.apache.org Received: (qmail 55384 invoked by uid 99); 12 Jun 2017 15:50:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Jun 2017 15:50:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 32B9218040F for ; Mon, 12 Jun 2017 15:50:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id giY-LoRDaqlC for ; Mon, 12 Jun 2017 15:50:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id C6FCE5FCA1 for ; Mon, 12 Jun 2017 15:50:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 55953E01D8 for ; Mon, 12 Jun 2017 15:50:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 0F1F621D8F for ; Mon, 12 Jun 2017 15:50:00 +0000 (UTC) Date: Mon, 12 Jun 2017 15:50:00 +0000 (UTC) From: "Jay Holloway (JIRA)" To: issues@karaf.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (KARAF-5187) Feature install runs 30 minutes and gets out of memory error in Felix resolver code MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 12 Jun 2017 15:50:05 -0000 [ https://issues.apache.org/jira/browse/KARAF-5187?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1604= 6706#comment-16046706 ]=20 Jay Holloway commented on KARAF-5187: ------------------------------------- I am not allowed to share our code; it is proprietary. Our feature file ha= s been working with few problems for over a year with Karaf 4.0.4 and 4.0.9= .=C2=A0 Recently, we added a lot of bundles (including wrapped jars) that s= eems to have stressed the resolver. Can you tell us if Karaf 4.1.1 address= ed critical resolver issues. =C2=A0We notice the following within the 4.1.1= RELEASE-NOTES.=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0 * [KARAF-4701] - Problem installing feature =C2=A0=C2=A0=C2=A0 =C2=A0* [KARAF-4967] - Upgrade to Felix Resolver 1.12.0 We have tested with Karaf 4.1.1 and know that it processes our feature file= with no problem.=C2=A0 However, upgrades go through a separate architectur= e team.=C2=A0 We are looking for some type of confirmation from you in orde= r to convince the architecture team that we need to officially upgrade to K= araf 4.1.1.=C2=A0=C2=A0=20 > Feature install runs 30 minutes and gets out of memory error in Felix res= olver code > -------------------------------------------------------------------------= ---------- > > Key: KARAF-5187 > URL: https://issues.apache.org/jira/browse/KARAF-5187 > Project: Karaf > Issue Type: Bug > Components: karaf-feature > Affects Versions: 4.0.9 > Environment: Linux > Reporter: Jay Holloway > > We are currently using Karaf 4.0.9. We have a feature file that has work= ed for us for over a year. We have noticed a slight degradation during the= feature install in the past few months as we have added bundles and sub-fe= atures to our feature file. Recently, we added numerous new sub-features a= nd bundles to our one feature file. Currently, the feature install hangs b= etween 15 and 45 minutes until we get a Java heap space out of memory error= . The print stack trace shows that it is in the Felix resolver the entire = time. However, when we downloaded, setup and configured Karaf 4.1.1, the s= ame feature file installed with no problem and very quickly. Is there some= thing we can do within Karaf 4.0.9 to make it process our feature file more= efficiently without hanging? Officially upgrading to Karaf 4.1.1 is out o= f our control.=20 -- This message was sent by Atlassian JIRA (v6.4.14#64029)