You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@karaf.apache.org by Michael Täschner <m....@gmail.com> on 2015/10/30 13:48:04 UTC
Bundle refresh issue on update to 3.0.5
Hi Karaf Users,
I recently upgraded from 3.0.4 to 3.0.5 (by ServiceMix upgrade from 6.0.0
to 6.0.1) and run into an issue with resolving fragments installed for a
previously installed bundle via feature descriptor at container start.
Dependencies are as shown below. Before the "base" bundle was refreshed on
installation of feature referencing the feature where the base bundle is
declared, whereas now the fragments remain in state "installed". On manual
refresh of "base" via console the fragments are resolved.
simple showcase:
<feature name="base" version="1.0.0" start-level="60">
... various bundles ...
<bundle>mvn:org.mitaes.base/core/1.0.0</bundle>
</feature>
<feature name="extender" version="1.0.0" start-level="60">
<feature>base</feature>
<bundle>mvn:org.mitaes.base/core-fragment1/1.0.0</bundle>
</feature>
Any idea which change in the karaf release may be related ?
Thanks and Best Regards,
Michael
Re: Bundle refresh issue on update to 3.0.5
Posted by Michael Täschner <m....@gmail.com>.
Hi JB,
thanks for looking into this.
Strangely enough this issue does not exist in ServiceMix 6.0.0 (based on
Karaf 3.0.4) but I can reproduce it in plain Apache-Karaf 3.0.4. We had no
previous issues in ServiceMix 5.x based on Karaf 2.3/2.4.
Best Regards,
Michael
2015-11-16 17:29 GMT+01:00 Jean-Baptiste Onofré <jb...@nanthrax.net>:
> Thanks
>
> Regards
> JB
>
> On 11/16/2015 05:28 PM, Michael Täschner wrote:
>
>> Hi JB,
>>
>> I raised issue KARAF-4116 [1] and attached an example to reproduce the
>> behavior.
>>
>> Best Regards,
>> Michael
>>
>> [1] https://issues.apache.org/jira/browse/KARAF-4116
>>
>> 2015-11-16 16:39 GMT+01:00 Jean-Baptiste Onofré <jb@nanthrax.net
>> <ma...@nanthrax.net>>:
>>
>> As you already have a test case, it's worth to create a Jira IMHO.
>>
>> Regards
>> JB
>>
>> On 11/16/2015 04:31 PM, Michael Täschner wrote:
>>
>> Hi JB,
>>
>> no I haven't raised an issue yet as I was first looking for
>> potential
>> feedback here in the karaf-users list. I can create one though.
>> I'll
>> have to prepare a test as currently we use the FeatureService for
>> installing a set of application services and the fragments are not
>> declared in etc/org.apache.karaf.features.cfg. But I think I can
>> provide
>> that ...
>>
>> Thanks and Best Regards,
>> Michael
>>
>> 2015-11-16 16:28 GMT+01:00 Jean-Baptiste Onofré <jb@nanthrax.net
>> <ma...@nanthrax.net>
>> <mailto:jb@nanthrax.net <ma...@nanthrax.net>>>:
>>
>>
>> Hi Michael,
>>
>> did you create a Jira about that or not yet ?
>>
>> Regards
>> JB
>>
>> On 11/16/2015 04:27 PM, Michael Täschner wrote:
>>
>> Hi,
>>
>> nobody else having the issue of Fragment-Host bundle
>> not being
>> refreshed
>> upon installation of feature containing fragment bundle
>> ? I tried
>> debugging
>> into
>>
>>
>> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(Set<Feature>,
>> EnumSet<Option>) and looks like the host bundle is
>> never added
>> to the
>> InstallationState bundle list for bundles to refresh
>> after
>> feature install ?
>>
>> Any help is welcome because currently the only
>> workaround is to
>> manually
>> refresh the referenced Fragment-Host bundle as the
>> fragment bundles
>> remain in "INSTALLED" state and no error being raised.
>>
>> Thanks and Best Regards,
>> Michael
>>
>> 2015-10-30 13:48 GMT+01:00 Michael Täschner
>> <m.taeschner@gmail.com <ma...@gmail.com>
>> <mailto:m.taeschner@gmail.com <ma...@gmail.com>>
>> <mailto:m.taeschner@gmail.com
>> <ma...@gmail.com> <mailto:m.taeschner@gmail.com
>> <ma...@gmail.com>>>>:
>>
>>
>> Hi Karaf Users,
>>
>> I recently upgraded from 3.0.4 to 3.0.5 (by
>> ServiceMix
>> upgrade from
>> 6.0.0 to 6.0.1) and run into an issue with
>> resolving fragments
>> installed for a previously installed bundle via
>> feature
>> descriptor
>> at container start. Dependencies are as shown
>> below. Before the
>> "base" bundle was refreshed on installation of
>> feature
>> referencing
>> the feature where the base bundle is declared,
>> whereas now the
>> fragments remain in state "installed". On manual
>> refresh of
>> "base"
>> via console the fragments are resolved.
>>
>> simple showcase:
>> <feature name="base" version="1.0.0"
>> start-level="60">
>> ... various bundles ...
>> <bundle>mvn:org.mitaes.base/core/1.0.0</bundle>
>> </feature>
>>
>> <feature name="extender" version="1.0.0"
>> start-level="60">
>> <feature>base</feature>
>>
>> <bundle>mvn:org.mitaes.base/core-fragment1/1.0.0</bundle>
>> </feature>
>>
>> Any idea which change in the karaf release may be
>> related ?
>>
>> Thanks and Best Regards,
>> Michael
>>
>>
>>
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org <ma...@apache.org>
>> <mailto:jbonofre@apache.org <ma...@apache.org>>
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>>
>>
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org <ma...@apache.org>
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>>
>>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: Bundle refresh issue on update to 3.0.5
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Thanks
Regards
JB
On 11/16/2015 05:28 PM, Michael Täschner wrote:
> Hi JB,
>
> I raised issue KARAF-4116 [1] and attached an example to reproduce the
> behavior.
>
> Best Regards,
> Michael
>
> [1] https://issues.apache.org/jira/browse/KARAF-4116
>
> 2015-11-16 16:39 GMT+01:00 Jean-Baptiste Onofré <jb@nanthrax.net
> <ma...@nanthrax.net>>:
>
> As you already have a test case, it's worth to create a Jira IMHO.
>
> Regards
> JB
>
> On 11/16/2015 04:31 PM, Michael Täschner wrote:
>
> Hi JB,
>
> no I haven't raised an issue yet as I was first looking for
> potential
> feedback here in the karaf-users list. I can create one though. I'll
> have to prepare a test as currently we use the FeatureService for
> installing a set of application services and the fragments are not
> declared in etc/org.apache.karaf.features.cfg. But I think I can
> provide
> that ...
>
> Thanks and Best Regards,
> Michael
>
> 2015-11-16 16:28 GMT+01:00 Jean-Baptiste Onofré <jb@nanthrax.net
> <ma...@nanthrax.net>
> <mailto:jb@nanthrax.net <ma...@nanthrax.net>>>:
>
> Hi Michael,
>
> did you create a Jira about that or not yet ?
>
> Regards
> JB
>
> On 11/16/2015 04:27 PM, Michael Täschner wrote:
>
> Hi,
>
> nobody else having the issue of Fragment-Host bundle
> not being
> refreshed
> upon installation of feature containing fragment bundle
> ? I tried
> debugging
> into
>
> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(Set<Feature>,
> EnumSet<Option>) and looks like the host bundle is
> never added
> to the
> InstallationState bundle list for bundles to refresh after
> feature install ?
>
> Any help is welcome because currently the only
> workaround is to
> manually
> refresh the referenced Fragment-Host bundle as the
> fragment bundles
> remain in "INSTALLED" state and no error being raised.
>
> Thanks and Best Regards,
> Michael
>
> 2015-10-30 13:48 GMT+01:00 Michael Täschner
> <m.taeschner@gmail.com <ma...@gmail.com>
> <mailto:m.taeschner@gmail.com <ma...@gmail.com>>
> <mailto:m.taeschner@gmail.com
> <ma...@gmail.com> <mailto:m.taeschner@gmail.com
> <ma...@gmail.com>>>>:
>
>
> Hi Karaf Users,
>
> I recently upgraded from 3.0.4 to 3.0.5 (by ServiceMix
> upgrade from
> 6.0.0 to 6.0.1) and run into an issue with
> resolving fragments
> installed for a previously installed bundle via
> feature
> descriptor
> at container start. Dependencies are as shown
> below. Before the
> "base" bundle was refreshed on installation of feature
> referencing
> the feature where the base bundle is declared,
> whereas now the
> fragments remain in state "installed". On manual
> refresh of
> "base"
> via console the fragments are resolved.
>
> simple showcase:
> <feature name="base" version="1.0.0" start-level="60">
> ... various bundles ...
> <bundle>mvn:org.mitaes.base/core/1.0.0</bundle>
> </feature>
>
> <feature name="extender" version="1.0.0"
> start-level="60">
> <feature>base</feature>
>
> <bundle>mvn:org.mitaes.base/core-fragment1/1.0.0</bundle>
> </feature>
>
> Any idea which change in the karaf release may be
> related ?
>
> Thanks and Best Regards,
> Michael
>
>
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org <ma...@apache.org>
> <mailto:jbonofre@apache.org <ma...@apache.org>>
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
>
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org <ma...@apache.org>
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Bundle refresh issue on update to 3.0.5
Posted by Michael Täschner <m....@gmail.com>.
Hi JB,
I raised issue KARAF-4116 [1] and attached an example to reproduce the
behavior.
Best Regards,
Michael
[1] https://issues.apache.org/jira/browse/KARAF-4116
2015-11-16 16:39 GMT+01:00 Jean-Baptiste Onofré <jb...@nanthrax.net>:
> As you already have a test case, it's worth to create a Jira IMHO.
>
> Regards
> JB
>
> On 11/16/2015 04:31 PM, Michael Täschner wrote:
>
>> Hi JB,
>>
>> no I haven't raised an issue yet as I was first looking for potential
>> feedback here in the karaf-users list. I can create one though. I'll
>> have to prepare a test as currently we use the FeatureService for
>> installing a set of application services and the fragments are not
>> declared in etc/org.apache.karaf.features.cfg. But I think I can provide
>> that ...
>>
>> Thanks and Best Regards,
>> Michael
>>
>> 2015-11-16 16:28 GMT+01:00 Jean-Baptiste Onofré <jb@nanthrax.net
>> <ma...@nanthrax.net>>:
>>
>> Hi Michael,
>>
>> did you create a Jira about that or not yet ?
>>
>> Regards
>> JB
>>
>> On 11/16/2015 04:27 PM, Michael Täschner wrote:
>>
>> Hi,
>>
>> nobody else having the issue of Fragment-Host bundle not being
>> refreshed
>> upon installation of feature containing fragment bundle ? I tried
>> debugging
>> into
>>
>> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(Set<Feature>,
>> EnumSet<Option>) and looks like the host bundle is never added
>> to the
>> InstallationState bundle list for bundles to refresh after
>> feature install ?
>>
>> Any help is welcome because currently the only workaround is to
>> manually
>> refresh the referenced Fragment-Host bundle as the fragment
>> bundles
>> remain in "INSTALLED" state and no error being raised.
>>
>> Thanks and Best Regards,
>> Michael
>>
>> 2015-10-30 13:48 GMT+01:00 Michael Täschner
>> <m.taeschner@gmail.com <ma...@gmail.com>
>> <mailto:m.taeschner@gmail.com <ma...@gmail.com>>>:
>>
>>
>> Hi Karaf Users,
>>
>> I recently upgraded from 3.0.4 to 3.0.5 (by ServiceMix
>> upgrade from
>> 6.0.0 to 6.0.1) and run into an issue with resolving
>> fragments
>> installed for a previously installed bundle via feature
>> descriptor
>> at container start. Dependencies are as shown below. Before
>> the
>> "base" bundle was refreshed on installation of feature
>> referencing
>> the feature where the base bundle is declared, whereas now
>> the
>> fragments remain in state "installed". On manual refresh of
>> "base"
>> via console the fragments are resolved.
>>
>> simple showcase:
>> <feature name="base" version="1.0.0" start-level="60">
>> ... various bundles ...
>> <bundle>mvn:org.mitaes.base/core/1.0.0</bundle>
>> </feature>
>>
>> <feature name="extender" version="1.0.0" start-level="60">
>> <feature>base</feature>
>> <bundle>mvn:org.mitaes.base/core-fragment1/1.0.0</bundle>
>> </feature>
>>
>> Any idea which change in the karaf release may be related ?
>>
>> Thanks and Best Regards,
>> Michael
>>
>>
>>
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org <ma...@apache.org>
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>>
>>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: Bundle refresh issue on update to 3.0.5
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
As you already have a test case, it's worth to create a Jira IMHO.
Regards
JB
On 11/16/2015 04:31 PM, Michael Täschner wrote:
> Hi JB,
>
> no I haven't raised an issue yet as I was first looking for potential
> feedback here in the karaf-users list. I can create one though. I'll
> have to prepare a test as currently we use the FeatureService for
> installing a set of application services and the fragments are not
> declared in etc/org.apache.karaf.features.cfg. But I think I can provide
> that ...
>
> Thanks and Best Regards,
> Michael
>
> 2015-11-16 16:28 GMT+01:00 Jean-Baptiste Onofré <jb@nanthrax.net
> <ma...@nanthrax.net>>:
>
> Hi Michael,
>
> did you create a Jira about that or not yet ?
>
> Regards
> JB
>
> On 11/16/2015 04:27 PM, Michael Täschner wrote:
>
> Hi,
>
> nobody else having the issue of Fragment-Host bundle not being
> refreshed
> upon installation of feature containing fragment bundle ? I tried
> debugging
> into
> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(Set<Feature>,
> EnumSet<Option>) and looks like the host bundle is never added
> to the
> InstallationState bundle list for bundles to refresh after
> feature install ?
>
> Any help is welcome because currently the only workaround is to
> manually
> refresh the referenced Fragment-Host bundle as the fragment bundles
> remain in "INSTALLED" state and no error being raised.
>
> Thanks and Best Regards,
> Michael
>
> 2015-10-30 13:48 GMT+01:00 Michael Täschner
> <m.taeschner@gmail.com <ma...@gmail.com>
> <mailto:m.taeschner@gmail.com <ma...@gmail.com>>>:
>
> Hi Karaf Users,
>
> I recently upgraded from 3.0.4 to 3.0.5 (by ServiceMix
> upgrade from
> 6.0.0 to 6.0.1) and run into an issue with resolving fragments
> installed for a previously installed bundle via feature
> descriptor
> at container start. Dependencies are as shown below. Before the
> "base" bundle was refreshed on installation of feature
> referencing
> the feature where the base bundle is declared, whereas now the
> fragments remain in state "installed". On manual refresh of
> "base"
> via console the fragments are resolved.
>
> simple showcase:
> <feature name="base" version="1.0.0" start-level="60">
> ... various bundles ...
> <bundle>mvn:org.mitaes.base/core/1.0.0</bundle>
> </feature>
>
> <feature name="extender" version="1.0.0" start-level="60">
> <feature>base</feature>
> <bundle>mvn:org.mitaes.base/core-fragment1/1.0.0</bundle>
> </feature>
>
> Any idea which change in the karaf release may be related ?
>
> Thanks and Best Regards,
> Michael
>
>
>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org <ma...@apache.org>
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Bundle refresh issue on update to 3.0.5
Posted by Michael Täschner <m....@gmail.com>.
Hi JB,
no I haven't raised an issue yet as I was first looking for potential
feedback here in the karaf-users list. I can create one though. I'll have
to prepare a test as currently we use the FeatureService for installing a
set of application services and the fragments are not declared in
etc/org.apache.karaf.features.cfg. But I think I can provide that ...
Thanks and Best Regards,
Michael
2015-11-16 16:28 GMT+01:00 Jean-Baptiste Onofré <jb...@nanthrax.net>:
> Hi Michael,
>
> did you create a Jira about that or not yet ?
>
> Regards
> JB
>
> On 11/16/2015 04:27 PM, Michael Täschner wrote:
>
>> Hi,
>>
>> nobody else having the issue of Fragment-Host bundle not being refreshed
>> upon installation of feature containing fragment bundle ? I tried
>> debugging
>> into
>> org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(Set<Feature>,
>> EnumSet<Option>) and looks like the host bundle is never added to the
>> InstallationState bundle list for bundles to refresh after feature
>> install ?
>>
>> Any help is welcome because currently the only workaround is to manually
>> refresh the referenced Fragment-Host bundle as the fragment bundles
>> remain in "INSTALLED" state and no error being raised.
>>
>> Thanks and Best Regards,
>> Michael
>>
>> 2015-10-30 13:48 GMT+01:00 Michael Täschner <m.taeschner@gmail.com
>> <ma...@gmail.com>>:
>>
>> Hi Karaf Users,
>>
>> I recently upgraded from 3.0.4 to 3.0.5 (by ServiceMix upgrade from
>> 6.0.0 to 6.0.1) and run into an issue with resolving fragments
>> installed for a previously installed bundle via feature descriptor
>> at container start. Dependencies are as shown below. Before the
>> "base" bundle was refreshed on installation of feature referencing
>> the feature where the base bundle is declared, whereas now the
>> fragments remain in state "installed". On manual refresh of "base"
>> via console the fragments are resolved.
>>
>> simple showcase:
>> <feature name="base" version="1.0.0" start-level="60">
>> ... various bundles ...
>> <bundle>mvn:org.mitaes.base/core/1.0.0</bundle>
>> </feature>
>>
>> <feature name="extender" version="1.0.0" start-level="60">
>> <feature>base</feature>
>> <bundle>mvn:org.mitaes.base/core-fragment1/1.0.0</bundle>
>> </feature>
>>
>> Any idea which change in the karaf release may be related ?
>>
>> Thanks and Best Regards,
>> Michael
>>
>>
>>
> --
> Jean-Baptiste Onofré
> jbonofre@apache.org
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Re: Bundle refresh issue on update to 3.0.5
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi Michael,
did you create a Jira about that or not yet ?
Regards
JB
On 11/16/2015 04:27 PM, Michael Täschner wrote:
> Hi,
>
> nobody else having the issue of Fragment-Host bundle not being refreshed
> upon installation of feature containing fragment bundle ? I tried
> debugging
> into org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(Set<Feature>,
> EnumSet<Option>) and looks like the host bundle is never added to the
> InstallationState bundle list for bundles to refresh after feature install ?
>
> Any help is welcome because currently the only workaround is to manually
> refresh the referenced Fragment-Host bundle as the fragment bundles
> remain in "INSTALLED" state and no error being raised.
>
> Thanks and Best Regards,
> Michael
>
> 2015-10-30 13:48 GMT+01:00 Michael Täschner <m.taeschner@gmail.com
> <ma...@gmail.com>>:
>
> Hi Karaf Users,
>
> I recently upgraded from 3.0.4 to 3.0.5 (by ServiceMix upgrade from
> 6.0.0 to 6.0.1) and run into an issue with resolving fragments
> installed for a previously installed bundle via feature descriptor
> at container start. Dependencies are as shown below. Before the
> "base" bundle was refreshed on installation of feature referencing
> the feature where the base bundle is declared, whereas now the
> fragments remain in state "installed". On manual refresh of "base"
> via console the fragments are resolved.
>
> simple showcase:
> <feature name="base" version="1.0.0" start-level="60">
> ... various bundles ...
> <bundle>mvn:org.mitaes.base/core/1.0.0</bundle>
> </feature>
>
> <feature name="extender" version="1.0.0" start-level="60">
> <feature>base</feature>
> <bundle>mvn:org.mitaes.base/core-fragment1/1.0.0</bundle>
> </feature>
>
> Any idea which change in the karaf release may be related ?
>
> Thanks and Best Regards,
> Michael
>
>
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: Bundle refresh issue on update to 3.0.5
Posted by Michael Täschner <m....@gmail.com>.
Hi,
nobody else having the issue of Fragment-Host bundle not being refreshed
upon installation of feature containing fragment bundle ? I tried debugging
into org.apache.karaf.features.internal.FeaturesServiceImpl.installFeatures(Set<Feature>,
EnumSet<Option>) and looks like the host bundle is never added to the
InstallationState bundle list for bundles to refresh after feature install ?
Any help is welcome because currently the only workaround is to manually
refresh the referenced Fragment-Host bundle as the fragment bundles remain
in "INSTALLED" state and no error being raised.
Thanks and Best Regards,
Michael
2015-10-30 13:48 GMT+01:00 Michael Täschner <m....@gmail.com>:
> Hi Karaf Users,
>
> I recently upgraded from 3.0.4 to 3.0.5 (by ServiceMix upgrade from 6.0.0
> to 6.0.1) and run into an issue with resolving fragments installed for a
> previously installed bundle via feature descriptor at container start.
> Dependencies are as shown below. Before the "base" bundle was refreshed on
> installation of feature referencing the feature where the base bundle is
> declared, whereas now the fragments remain in state "installed". On manual
> refresh of "base" via console the fragments are resolved.
>
> simple showcase:
> <feature name="base" version="1.0.0" start-level="60">
> ... various bundles ...
> <bundle>mvn:org.mitaes.base/core/1.0.0</bundle>
> </feature>
>
> <feature name="extender" version="1.0.0" start-level="60">
> <feature>base</feature>
> <bundle>mvn:org.mitaes.base/core-fragment1/1.0.0</bundle>
> </feature>
>
> Any idea which change in the karaf release may be related ?
>
> Thanks and Best Regards,
> Michael
>