Return-Path: X-Original-To: apmail-activemq-dev-archive@www.apache.org Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id D877010B98 for ; Wed, 28 Aug 2013 14:06:54 +0000 (UTC) Received: (qmail 72487 invoked by uid 500); 28 Aug 2013 14:06:54 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 72127 invoked by uid 500); 28 Aug 2013 14:06:53 -0000 Mailing-List: contact dev-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 dev@activemq.apache.org Received: (qmail 72066 invoked by uid 99); 28 Aug 2013 14:06:53 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Aug 2013 14:06:53 +0000 Date: Wed, 28 Aug 2013 14:06:53 +0000 (UTC) From: "Dejan Bosanac (JIRA)" To: dev@activemq.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (AMQ-3778) Improve activemq-core osgi activator 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-3778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dejan Bosanac resolved AMQ-3778. -------------------------------- Resolution: Fixed Fix Version/s: (was: 5.9.0) 5.8.0 This is already fixed in 5.8 > Improve activemq-core osgi activator > ------------------------------------ > > Key: AMQ-3778 > URL: https://issues.apache.org/jira/browse/AMQ-3778 > Project: ActiveMQ > Issue Type: Improvement > Affects Versions: 5.5.0 > Reporter: Dejan Bosanac > Assignee: Dejan Bosanac > Fix For: 5.8.0 > > > Currently the activator keeps track of all bundles, so it can be used as a amq service factory when creating transports and such. The problem occurs when a bundle with connection factory that uses a transport is started before the bundle that implements that transport. Connection creation will fail in this case. We need to support configuring activator (presumably using config admin) to wait for certain transports to become available or introduce timeouts and retries to deal with this case. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira