[
https://issues.apache.org/jira/browse/KARAF-3888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14651646#comment-14651646
]
Christian Schneider commented on KARAF-3888:
--------------------------------------------
These are the root causes of the many refreshes:
jline/2.12.1 (Wired to org.apache.activemq.activemq-osgi/5.11.0.SNAPSHOT
which is being refreshed)
org.apache.activemq.activemq-osgi/5.11.0.SNAPSHOT (Wired to
org.apache.aries.transaction.manager/1.0.0 which is being refreshed)
org.apache.aries.transaction.manager/1.0.0 (Should be wired to:
org.apache.geronimo.specs.geronimo-jta_1.1_spec/1.1.1 (through
[org.apache.aries.transaction.manager/1.0.0] osgi.wiring.package;
filter:="(&(osgi.wiring.package=javax.transaction)(version>=1.1.0)(!(version>=2.0.0)))"))
transaction.manager is rewired to another spec version. This already causes all
bundles wired to the jta spec version embedded in transaction.manager to
restart.
One of these is activemq-osgi. The biggest problem now is that jline is wired
to activemq-osgi which is then also restarted. Restart of jline causes the
karaf shell to restart.
The wiring to jline is wrong and could be caused by
https://issues.apache.org/jira/browse/AMQ-5821 . This issue should already be
fixed. Will dig into why it is still present.
> Karaf refreshes a lot of unrelated bundles during feature installation
> ----------------------------------------------------------------------
>
> Key: KARAF-3888
> URL: https://issues.apache.org/jira/browse/KARAF-3888
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
> Affects Versions: 4.0.0
> Reporter: Ievgen Tarasov
> Assignee: Christian Schneider
> Attachments: karaf-refresh-problem
>
>
> To reproduce the problem:
> {noformat}
> feature:repo-add mvn:org.apache.cxf.karaf/apache-cxf/3.1.1/xml/features
> feature:repo-add mvn:org.apache.camel.karaf/apache-camel/2.15.2/xml/features
> feature:repo-add
> mvn:org.apache.activemq/activemq-karaf/5.11-SNAPSHOT/xml/features
> feature:install activemq
> feature:install activemq-client
> feature:install camel
> feature:install cxf
> feature:install -v -t cxf-ws-policy
> {noformat}
> The result of the last command is in file [^karaf-refresh-problem] which is
> attached to this bug. In short:
> {noformat}
> karaf@root()> feature:install -v -t cxf-ws-policy
> Adding features: cxf-ws-policy/[3.1.1,3.1.1]
> No deployment change.
> Bundles to refresh:
> activemq-karaf/5.11.0.SNAPSHOT (Wired to
> org.apache.activemq.activemq-osgi/5.11.0.SNAPSHOT which is being refreshed)
> javax.mail/1.4.4 (Wired to
> org.apache.activemq.activemq-osgi/5.11.0.SNAPSHOT which is being refreshed)
> jline/2.12.1 (Wired to org.apache.activemq.activemq-osgi/5.11.0.SNAPSHOT
> which is being refreshed)
> net.sf.ehcache/2.9.0 (Wired to org.apache.aries.transaction.manager/1.0.0
> which is being refreshed)
> (about 90 other bundles)
> karaf@root()>
> {noformat}
> In the same time, if I slightly change the order of feature installation
> (install activemq-client _before_ activemq), then the refresh doesn't happen:
> {noformat}
> karaf@root()> feature:install -v -t cxf-ws-policy
> Adding features: cxf-ws-policy/[3.1.1,3.1.1]
> No deployment change.
> karaf@root()>
> {noformat}
> Note regarding AMQ vesrion - I'm using 5.11-SNAPSHOT because of a fix for
> another bundle refresh problem: https://issues.apache.org/jira/browse/AMQ-5821
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
