You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@karaf.apache.org by Krzysztof Sobkowiak <kr...@gmail.com> on 2014/07/29 22:10:38 UTC
Problem with respectStartLvlDuringFeatureStartup (was: [VOTE] Release
Apache Karaf 2.3.6)
Hi
I'm testing ServiceMix after upgrade to the latest 2.3.6-SNAPSHOT. I
think, there is no difference between 2.3.6 and 2.3.6-SNAPSHOT. It looks
very good, our most problems have been fixed, but I have found one
problem I want to describe here. You can answer whether it is a new
issue in Karaf or whether we do something wrong.
After upgrade to ActiveMQ 5.9.1 we have found a problem when we wanted
to start activiti feature in featuresBoot. At startup we got following error
java.lang.Exception: Could not start bundle
mvn:org.activiti/activiti-engine/5.15.1 in feature(s) activiti-5.15.1:
Uses constraint violation. Unable to resolve bundle revision
org.activiti.engine [187.0] because it is exposed to package
'org.joda.time.format' from bundle revisions
org.apache.servicemix.bundles.joda-time [56.0] and joda-time [106.0] via
two dependency chains.
Chain 1:
org.activiti.engine [187.0]
import:
(&(osgi.wiring.package=org.joda.time.format)(version>=2.1.0)(!(version>=3.0.0)))
|
export: osgi.wiring.package=org.joda.time.format
org.apache.servicemix.bundles.joda-time [56.0]
Chain 2:
org.activiti.engine [187.0]
import:
(&(osgi.wiring.package=org.drools.runtime)(version>=5.5.0)(!(version>=6.0.0)))
|
export: osgi.wiring.package=org.drools.runtime;
uses:=com.thoughtworks.xstream.annotations
org.apache.servicemix.bundles.drools [179.0]
import: (osgi.wiring.package=com.thoughtworks.xstream.annotations)
|
export: osgi.wiring.package=com.thoughtworks.xstream.annotations;
uses:=org.joda.time.format
org.apache.servicemix.bundles.xstream [107.0]
import:
(&(osgi.wiring.package=org.joda.time.format)(version>=1.6.0)(!(version>=3.0.0)))
|
export: osgi.wiring.package=org.joda.time.format
joda-time [106.0]
It happend when we ServiceMix was based on Karaf 2.3.5. To solve this
problem we forced the start of the bundle
org.apache.servicemix.bundles.joda-timeat the beginning. We have created
following feature and added it at featuresBoot.
<feature name="joda-time">
<bundle
start-level='10'>mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.joda-time/${jodatime.bundle.version}</bundle>
</feature>
We have also set the parameter respectStartLvlDuringFeatureStartup to
true. It solved our problem andorg.apache.servicemix.bundles.xstream
could resolve the package from org.apache.servicemix.bundles.joda-time.
I don't know if it was correct solution but it solved our problem.
Next we had to downgrade to Karaf 2.3.4 (due to another problem
introduced in 2.3.5). Because Karaf 2.3.4 does not support the
respectStartLvlDuringFeatureStartup parameter, our solution didn't work
anymore an we had to add this bundle to startup.properties. It worked.
Now we want to upgrade to Karaf 2.3.6. I have removed the joda bundle
from startup.properties and our problem exists again - the solution
which worked with Karaf 2.3.5 doesn't work with 2.3.6. Moreover, when I
set respectStartLvlDuringFeatureStartup to false, the problem seems to
be fixed. Downgrade to Karaf 2.3.5 solves the problem too.
Have you changed something in the features installer and the logic of
respectStartLvlDuringFeatureStartup? Is our solution correct or should
we allways use startup.properties to force bundles to be installed
before other features are installed. I suppose, the answer for my
second question will be /yes/, but I'd like to know why our solution
with additional feature doesn't work anymore with Karaf 2.3.6.
Best regards
Krzysztof
On 29.07.2014 04:39, Jamie G. wrote:
> Hi,
>
> We resolved 70 issues in this release:
> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/community/download/karaf-2.3.6-release.page?view=markup
>
> Dependency changes can be reviewed here:
> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/documentation/karaf-dependencies/karaf-deps-2.3.x.page?revision=1613719&view=markup
>
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachekaraf-1008/
>
> Git tag:
> karaf-2.3.6
>
> Please vote to approve this release:
>
> [ ] +1 Approve the release
> [ ] -1 Veto the release (please provide specific comments)
>
> This vote will be open for 72 hours.
--
Krzysztof Sobkowiak
JEE & OSS Architect | Senior Solution Architect @ Capgemini | Committer
@ ASF
Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
<http://www.pl.capgemini-sdm.com/> | Wroclaw
e-mail: krzys.sobkowiak@gmail.com <ma...@gmail.com> |
Twitter: @KSobkowiak
Calendar: http://goo.gl/yvsebC
Re: Problem with respectStartLvlDuringFeatureStartup
Posted by Krzysztof Sobkowiak <kr...@gmail.com>.
Hi
I have tested ServiceMix 6.0.x which is based on Karaf 3.0.x. With Karaf
3.0.1 we have solved the problem similar to the ServiceMix based on
Karaf 2.3.5. With Karaf 2.3.6-SNAPSHOT this solution doesn't work
anymore too (see https://issues.apache.org/jira/browse/SM-2358)
Best regards
Krzysztof
On 29.07.2014 22:11, Krzysztof Sobkowiak wrote:
> You can see more details in
> https://issues.apache.org/jira/browse/SM-2301 and
> https://issues.apache.org/jira/browse/SM-2330
>
> On 29.07.2014 22:10, Krzysztof Sobkowiak wrote:
>> Hi
>>
>> I'm testing ServiceMix after upgrade to the latest 2.3.6-SNAPSHOT. I
>> think, there is no difference between 2.3.6 and 2.3.6-SNAPSHOT. It
>> looks very good, our most problems have been fixed, but I have found
>> one problem I want to describe here. You can answer whether it is a
>> new issue in Karaf or whether we do something wrong.
>>
>> After upgrade to ActiveMQ 5.9.1 we have found a problem when we
>> wanted to start activiti feature in featuresBoot. At startup we got
>> following error
>>
>>
>> java.lang.Exception: Could not start bundle
>> mvn:org.activiti/activiti-engine/5.15.1 in feature(s)
>> activiti-5.15.1: Uses constraint violation. Unable to resolve bundle
>> revision org.activiti.engine [187.0] because it is exposed to package
>> 'org.joda.time.format' from bundle revisions
>> org.apache.servicemix.bundles.joda-time [56.0] and joda-time [106.0]
>> via two dependency chains.
>>
>> Chain 1:
>> org.activiti.engine [187.0]
>> import:
>> (&(osgi.wiring.package=org.joda.time.format)(version>=2.1.0)(!(version>=3.0.0)))
>> |
>> export: osgi.wiring.package=org.joda.time.format
>> org.apache.servicemix.bundles.joda-time [56.0]
>>
>> Chain 2:
>> org.activiti.engine [187.0]
>> import:
>> (&(osgi.wiring.package=org.drools.runtime)(version>=5.5.0)(!(version>=6.0.0)))
>> |
>> export: osgi.wiring.package=org.drools.runtime;
>> uses:=com.thoughtworks.xstream.annotations
>> org.apache.servicemix.bundles.drools [179.0]
>> import: (osgi.wiring.package=com.thoughtworks.xstream.annotations)
>> |
>> export: osgi.wiring.package=com.thoughtworks.xstream.annotations;
>> uses:=org.joda.time.format
>> org.apache.servicemix.bundles.xstream [107.0]
>> import:
>> (&(osgi.wiring.package=org.joda.time.format)(version>=1.6.0)(!(version>=3.0.0)))
>> |
>> export: osgi.wiring.package=org.joda.time.format
>> joda-time [106.0]
>>
>>
>> It happend when we ServiceMix was based on Karaf 2.3.5. To solve this
>> problem we forced the start of the bundle
>> org.apache.servicemix.bundles.joda-timeat the beginning. We have
>> created following feature and added it at featuresBoot.
>>
>> <feature name="joda-time">
>> <bundle
>> start-level='10'>mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.joda-time/${jodatime.bundle.version}</bundle>
>> </feature>
>>
>> We have also set the parameter respectStartLvlDuringFeatureStartup to
>> true. It solved our problem andorg.apache.servicemix.bundles.xstream
>> could resolve the package from
>> org.apache.servicemix.bundles.joda-time. I don't know if it was
>> correct solution but it solved our problem.
>>
>> Next we had to downgrade to Karaf 2.3.4 (due to another problem
>> introduced in 2.3.5). Because Karaf 2.3.4 does not support the
>> respectStartLvlDuringFeatureStartup parameter, our solution didn't
>> work anymore an we had to add this bundle to startup.properties. It
>> worked.
>>
>> Now we want to upgrade to Karaf 2.3.6. I have removed the joda bundle
>> from startup.properties and our problem exists again - the solution
>> which worked with Karaf 2.3.5 doesn't work with 2.3.6. Moreover, when
>> I set respectStartLvlDuringFeatureStartup to false, the problem
>> seems to be fixed. Downgrade to Karaf 2.3.5 solves the problem too.
>>
>> Have you changed something in the features installer and the logic of
>> respectStartLvlDuringFeatureStartup? Is our solution correct or
>> should we allways use startup.properties to force bundles to be
>> installed before other features are installed. I suppose, the answer
>> for my second question will be /yes/, but I'd like to know why our
>> solution with additional feature doesn't work anymore with Karaf 2.3.6.
>>
>>
>> Best regards
>> Krzysztof
>>
>>
>
>
> --
> Krzysztof Sobkowiak
>
> JEE & OSS Architect | Senior Solution Architect @ Capgemini |
> Committer @ ASF
> Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
> <http://www.pl.capgemini-sdm.com/> | Wroclaw
> e-mail: krzys.sobkowiak@gmail.com <ma...@gmail.com> |
> Twitter: @KSobkowiak
> Calendar: http://goo.gl/yvsebC
--
Krzysztof Sobkowiak
JEE & OSS Architect | Senior Solution Architect @ Capgemini | Committer
@ ASF
Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
<http://www.pl.capgemini-sdm.com/> | Wroclaw
e-mail: krzys.sobkowiak@gmail.com <ma...@gmail.com> |
Twitter: @KSobkowiak
Calendar: http://goo.gl/yvsebC
Re: Problem with respectStartLvlDuringFeatureStartup
Posted by Krzysztof Sobkowiak <kr...@gmail.com>.
You can see more details in
https://issues.apache.org/jira/browse/SM-2301 and
https://issues.apache.org/jira/browse/SM-2330
On 29.07.2014 22:10, Krzysztof Sobkowiak wrote:
> Hi
>
> I'm testing ServiceMix after upgrade to the latest 2.3.6-SNAPSHOT. I
> think, there is no difference between 2.3.6 and 2.3.6-SNAPSHOT. It
> looks very good, our most problems have been fixed, but I have found
> one problem I want to describe here. You can answer whether it is a
> new issue in Karaf or whether we do something wrong.
>
> After upgrade to ActiveMQ 5.9.1 we have found a problem when we wanted
> to start activiti feature in featuresBoot. At startup we got following
> error
>
>
> java.lang.Exception: Could not start bundle
> mvn:org.activiti/activiti-engine/5.15.1 in feature(s) activiti-5.15.1:
> Uses constraint violation. Unable to resolve bundle revision
> org.activiti.engine [187.0] because it is exposed to package
> 'org.joda.time.format' from bundle revisions
> org.apache.servicemix.bundles.joda-time [56.0] and joda-time [106.0]
> via two dependency chains.
>
> Chain 1:
> org.activiti.engine [187.0]
> import:
> (&(osgi.wiring.package=org.joda.time.format)(version>=2.1.0)(!(version>=3.0.0)))
> |
> export: osgi.wiring.package=org.joda.time.format
> org.apache.servicemix.bundles.joda-time [56.0]
>
> Chain 2:
> org.activiti.engine [187.0]
> import:
> (&(osgi.wiring.package=org.drools.runtime)(version>=5.5.0)(!(version>=6.0.0)))
> |
> export: osgi.wiring.package=org.drools.runtime;
> uses:=com.thoughtworks.xstream.annotations
> org.apache.servicemix.bundles.drools [179.0]
> import: (osgi.wiring.package=com.thoughtworks.xstream.annotations)
> |
> export: osgi.wiring.package=com.thoughtworks.xstream.annotations;
> uses:=org.joda.time.format
> org.apache.servicemix.bundles.xstream [107.0]
> import:
> (&(osgi.wiring.package=org.joda.time.format)(version>=1.6.0)(!(version>=3.0.0)))
> |
> export: osgi.wiring.package=org.joda.time.format
> joda-time [106.0]
>
>
> It happend when we ServiceMix was based on Karaf 2.3.5. To solve this
> problem we forced the start of the bundle
> org.apache.servicemix.bundles.joda-timeat the beginning. We have
> created following feature and added it at featuresBoot.
>
> <feature name="joda-time">
> <bundle
> start-level='10'>mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.joda-time/${jodatime.bundle.version}</bundle>
> </feature>
>
> We have also set the parameter respectStartLvlDuringFeatureStartup to
> true. It solved our problem andorg.apache.servicemix.bundles.xstream
> could resolve the package from
> org.apache.servicemix.bundles.joda-time. I don't know if it was
> correct solution but it solved our problem.
>
> Next we had to downgrade to Karaf 2.3.4 (due to another problem
> introduced in 2.3.5). Because Karaf 2.3.4 does not support the
> respectStartLvlDuringFeatureStartup parameter, our solution didn't
> work anymore an we had to add this bundle to startup.properties. It
> worked.
>
> Now we want to upgrade to Karaf 2.3.6. I have removed the joda bundle
> from startup.properties and our problem exists again - the solution
> which worked with Karaf 2.3.5 doesn't work with 2.3.6. Moreover, when
> I set respectStartLvlDuringFeatureStartup to false, the problem seems
> to be fixed. Downgrade to Karaf 2.3.5 solves the problem too.
>
> Have you changed something in the features installer and the logic of
> respectStartLvlDuringFeatureStartup? Is our solution correct or should
> we allways use startup.properties to force bundles to be installed
> before other features are installed. I suppose, the answer for my
> second question will be /yes/, but I'd like to know why our solution
> with additional feature doesn't work anymore with Karaf 2.3.6.
>
>
> Best regards
> Krzysztof
>
>
>
>
>
>
>
>
> On 29.07.2014 04:39, Jamie G. wrote:
>> Hi,
>>
>> We resolved 70 issues in this release:
>> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/community/download/karaf-2.3.6-release.page?view=markup
>>
>> Dependency changes can be reviewed here:
>> http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/documentation/karaf-dependencies/karaf-deps-2.3.x.page?revision=1613719&view=markup
>>
>> Staging repository:
>> https://repository.apache.org/content/repositories/orgapachekaraf-1008/
>>
>> Git tag:
>> karaf-2.3.6
>>
>> Please vote to approve this release:
>>
>> [ ] +1 Approve the release
>> [ ] -1 Veto the release (please provide specific comments)
>>
>> This vote will be open for 72 hours.
>
>
> --
> Krzysztof Sobkowiak
>
> JEE & OSS Architect | Senior Solution Architect @ Capgemini |
> Committer @ ASF
> Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
> <http://www.pl.capgemini-sdm.com/> | Wroclaw
> e-mail: krzys.sobkowiak@gmail.com <ma...@gmail.com> |
> Twitter: @KSobkowiak
> Calendar: http://goo.gl/yvsebC
--
Krzysztof Sobkowiak
JEE & OSS Architect | Senior Solution Architect @ Capgemini | Committer
@ ASF
Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
<http://www.pl.capgemini-sdm.com/> | Wroclaw
e-mail: krzys.sobkowiak@gmail.com <ma...@gmail.com> |
Twitter: @KSobkowiak
Calendar: http://goo.gl/yvsebC