Return-Path: <issues-return-30893-archive-asf-public=cust-asf.ponee.io@karaf.apache.org>
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 480C7200B6D
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Tue, 23 Aug 2016 19:15:24 +0200 (CEST)
Received: by cust-asf.ponee.io (Postfix)
	id 46B50160A81; Tue, 23 Aug 2016 17:15:24 +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 93D87160ABF
	for <archive-asf-public@cust-asf.ponee.io>; Tue, 23 Aug 2016 19:15:23 +0200 (CEST)
Received: (qmail 78316 invoked by uid 500); 23 Aug 2016 17:15:22 -0000
Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@karaf.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@karaf.apache.org>
List-Post: <mailto:issues@karaf.apache.org>
List-Id: <issues.karaf.apache.org>
Reply-To: dev@karaf.apache.org
Delivered-To: mailing list issues@karaf.apache.org
Received: (qmail 78304 invoked by uid 99); 23 Aug 2016 17:15:22 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 23 Aug 2016 17:15:22 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 90D872C0153
	for <issues@karaf.apache.org>; Tue, 23 Aug 2016 17:15:22 +0000 (UTC)
Date: Tue, 23 Aug 2016 17:15:22 +0000 (UTC)
From: =?utf-8?Q?Jean-Baptiste_Onofr=C3=A9_=28JIRA=29?= <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: <JIRA.12924025.1450885630000.385805.1471972522590@Atlassian.JIRA>
In-Reply-To: <JIRA.12924025.1450885630000@Atlassian.JIRA>
References: <JIRA.12924025.1450885630000@Atlassian.JIRA> <JIRA.12924025.1450885630141@arcas>
Subject: [jira] [Updated] (KARAF-4237) can't install transaction feature and
 activemq-camel feature: Missing dependency
 javax.transaction.TransactionManager
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
archived-at: Tue, 23 Aug 2016 17:15:24 -0000


     [ https://issues.apache.org/jira/browse/KARAF-4237?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jean-Baptiste Onofr=C3=A9 updated KARAF-4237:
----------------------------------------
    Fix Version/s:     (was: 4.0.6)
                   4.0.7

> can't install transaction feature and activemq-camel feature: Missing dep=
endency javax.transaction.TransactionManager
> -------------------------------------------------------------------------=
--------------------------------------------
>
>                 Key: KARAF-4237
>                 URL: https://issues.apache.org/jira/browse/KARAF-4237
>             Project: Karaf
>          Issue Type: Bug
>    Affects Versions: 4.0.3
>         Environment: ubuntu 14.04, java 7 update 79 (also tried with java=
 8 update 45), karaf 3.0.3 camel 2.16.1, activemq 5.13.0
>            Reporter: Edward Welch
>             Fix For: 4.1.0, 4.0.7
>
>
> I found a little bit of a strange behavior, which I think points to a pos=
sible bug in the features dependency resolver?
> Easiest way to reproduce, start with a vanilla 4.0.3
> feature:repo-add activemq 5.13.0
> feature:repo-add camel 2.16.1
> feature:install transaction activemq-camel
> bundle:diag
> You will see both Apache Aries Transaction Blueprint bundles in Grace Per=
iod waiting for javax.transaction.TransactionManager
> Pretty sure this is caused by some bad wiring on a bundle which activemq-=
camel brings in, here is that feature descriptor:
> {code}
> <feature name=3D'camel-jms' version=3D'${project.version}' resolver=3D'(o=
br)' start-level=3D'50'>
>     <feature version=3D'${spring-version-range-karaf}'>spring</feature>
>     <bundle dependency=3D'true'>mvn:org.apache.geronimo.specs/geronimo-jt=
a_1.1_spec/${geronimo-jta-spec-version}</bundle>
>     <bundle dependency=3D'true'>mvn:commons-pool/commons-pool/${commons-p=
ool-version}</bundle>
>     <bundle dependency=3D'true'>mvn:org.apache.geronimo.specs/geronimo-jm=
s_1.1_spec/${geronimo-jms-spec-version}</bundle>
>     <feature version=3D'${spring-version-range-karaf}'>spring-jms</featur=
e>
>     <feature version=3D'${project.version}'>camel-core</feature>
>     <bundle>mvn:org.apache.camel/camel-jms/${project.version}</bundle>
> </feature>
> {code}
> I see the aries transaction bundles being wired to this bundle coming fro=
m the activemq-camel feature: mvn:org.apache.geronimo.specs/geronimo-jta_1.=
1_spec/${geronimo-jta-spec-version}
> What's strange about this, that bundle is marked dependency=3D"true" so I=
 would think it wouldn't need to be installed at all.
> Also peculiar, if you follow this install order:
> feature:repo-add activemq 5.13.0
> feature:repo-add camel 2.16.1
> feature:install transaction
> feature:install activemq-camel
> bundle:diag
> There is no issue, so the re-wiring/refresh of the transaction bundles ne=
ver happens
> Also when I originally posted this on the mailing list:=20
> http://karaf.922171.n3.nabble.com/Missing-dependency-javax-transaction-Tr=
ansactionManager-with-transaction-feature-and-activemq-camel-td4044354.html
> Christian Schneider was unable to reproduce the issue, even though it occ=
urs 100% of the time for me, so maybe there is something else in play here =
that I can't think of.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)