Return-Path: X-Original-To: apmail-activemq-issues-archive@minotaur.apache.org Delivered-To: apmail-activemq-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E6AF117EC9 for ; Wed, 3 Jun 2015 13:38:38 +0000 (UTC) Received: (qmail 18522 invoked by uid 500); 3 Jun 2015 13:38:38 -0000 Delivered-To: apmail-activemq-issues-archive@activemq.apache.org Received: (qmail 18495 invoked by uid 500); 3 Jun 2015 13:38:38 -0000 Mailing-List: contact issues-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list issues@activemq.apache.org Received: (qmail 18485 invoked by uid 99); 3 Jun 2015 13:38:38 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Jun 2015 13:38:38 +0000 Date: Wed, 3 Jun 2015 13:38:38 +0000 (UTC) From: "Christian Schneider (JIRA)" To: issues@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMQ-5821) Activator can trigger unwanted behaviour when loading classes from other bundles MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMQ-5821?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider updated AMQ-5821: ------------------------------------- Fix Version/s: 5.12.0 5.11.2 > Activator can trigger unwanted behaviour when loading classes from other bundles > -------------------------------------------------------------------------------- > > Key: AMQ-5821 > URL: https://issues.apache.org/jira/browse/AMQ-5821 > Project: ActiveMQ > Issue Type: Bug > Components: Broker > Affects Versions: 5.11.1 > Reporter: Christian Schneider > Fix For: 5.11.2, 5.12.0 > > > Currently org.apache.activemq.util.osgi.Activator watches all other bundles and tries to load some classes using their classloader to check if they might implement extensions. > This can go wrong if the bundle uses dynamic imports like e.g. jline does. In this case the jline bundle is triggered to load classes from ActiveMQ. This establishes a wiring from jline to ActiveMQ. If the ActiveMQ bundle are now refreshed or uninstalled jline also has to be refreshed which triggers refreshs of a lot more bundles. > I propose to replace the class probing with checking of the bundle requirements. We simply check if the bundle has an import for the packages of the interface classes of ActiveMQ. So we avoid triggering classloading and the creation of unwanted wirings. -- This message was sent by Atlassian JIRA (v6.3.4#6332)