Re: Avoid unwanted refresh of bundles wired to activemq or cxf features

Hi Arnaud, As I guess you are using the Talend runtime, can you please send the kar to me (using jbono...@apache.org). I will investigate. Thanks, Regards JB On 10/19/2017 04:50 PM, Arnaud Geslin wrote: OK, so I unzipped the kar file and got 2 files : / /

Re: Avoid unwanted refresh of bundles wired to activemq or cxf features

OK, so I unzipped the kar file and got 2 files : repository/gfc/R_FRONTAL_HTTP/R_FRONTAL_HTTP/0.2/R_FRONTAL_HTTP-0.2.jarrepository/gfc/R_FRONTAL_HTTP/R_FRONTAL_HTTP-feature/0.2/R_FRONTAL_HTTP-feature-0.2.xml the xml file contains some tags for features dependencies, some tags for Talend

Re: Avoid unwanted refresh of bundles wired to activemq or cxf features

The noAutoRefreshBundles should work "on the fly", the restart will perform a refresh as it's a new wiring. Can you do the feature:install -t -v on a freshly installed Karaf (as it needs to call with an "empty" features set) ? A kar is basically a zip file containing a features XML. So

Re: Avoid unwanted refresh of bundles wired to activemq or cxf features

Hi Jean-Baptiste, Thanks for the reply. Unfortunatly, theses options don't give more info : karaf@trun()> feature:uninstall R_FRONTAL_HTTP-feature karaf@trun()> karaf@trun()> feature:install -t -v R_FRONTAL_HTTP-feature Adding features: R_FRONTAL_HTTP-feature/[0.2.0,0.2.0] karaf@trun()> > You

Re: Avoid unwanted refresh of bundles wired to activemq or cxf features

Hi Arnaud, It's what I said in my previous message. It's possible that the refresh comes from an optional import wired. So, to identify this, I would recommend to use feature:install -t -v to get the complete resolver output and identify the early first cause. Then, a simple workaround is to

Re: Avoid unwanted refresh of bundles wired to activemq or cxf features

Hi Guillaume. > So you need to find why the activemq-osgi bundle is refreshed, and so on. I'm not sure to use the right way to trace back, but it appears nowhere else in the logs than in "(Wired to org.apache.activemq.activemq-osgi/5.14.1 which is being refreshed)". Refreshing this bundle had

NPE on FeaturesServiceImpl$2.filterMatches()

Hello, I am using Karaf 4.1.2 with the latest snapshot 4.1.3 for the bundle features-core. I was missing in my karaf distribution the configuration of the 'endorsed' folder. I have added in my "core" kar archive tags in order to fix this. However, since this modification, I have randomly a

Re: Avoid unwanted refresh of bundles wired to activemq or cxf features

The bundle refresh are cascading, so in order to find the cause, you need to trace back the tree. In your example you have *activemq-karaf/5.14.1 (Wired to org.apache.activemq.activemq-osgi/5.14.1 which is being refreshed)* So you need to find why the *activemq-osgi* bundle is refreshed, and so

Re: Avoid unwanted refresh of bundles wired to activemq or cxf features

Hi Arnaud, You can disable the auto-refresh (on kar or feature) to avoid this. Can you do a feature:install -t -v to check the cause of the refresh (optional import I bet) ? Regards JB On 10/19/2017 11:13 AM, Arnaud Geslin wrote: Hello We build kar files with Talend studio (some Camel

Avoid unwanted refresh of bundles wired to activemq or cxf features

Hello We build kar files with Talend studio (some Camel routes) that are completly independent. When deploying thoses files by copy in container/deploy of by "bundle:install file://..." in the console, it sometimes refreshes all the other bundles already installed and active.

Re: [Karaf 4.1.2] - error with camel-elasticsearch5

Hi, Good news ! Thanks, On 19/10/2017 09:57, Jean-Baptiste Onofré wrote: > Hi, > > I just checked and I already fixed this issue (an export was missing > in the ServiceMix Elasticsearch bundle). > > Now the elasticsearch bundle ships transport, client, sniff packages, > no need to add a