[jira] [Updated] (KARAF-3748) Installing activemq-blueprint feature sometimes fails with uses constraint violation

2015-05-29 Thread Christian Schneider (JIRA) 

 [ 
https://issues.apache.org/jira/browse/KARAF-3748?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Christian Schneider updated KARAF-3748:
---
Summary: Installing activemq-blueprint feature sometimes fails with uses 
constraint violation  (was: Possible Constraint Violation when installing 
activemq-blueprint feature)

 Installing activemq-blueprint feature sometimes fails with uses constraint 
 violation
 

 Key: KARAF-3748
 URL: https://issues.apache.org/jira/browse/KARAF-3748
 Project: Karaf
  Issue Type: Bug
  Components: karaf-core
Affects Versions: 4.0.0.M3
Reporter: Achim Finke

 From time to time you get the following exception when installing 
 activemq-blueprint feature. 
 {code}
 org.osgi.service.resolver.ResolutionException: Uses constraint violation. 
 Unable to resolve resource org.apache.activemq.activemq-blueprint 
 [org.apache.activemq.activemq-blueprint/5.11.1] because it is exposed to 
 package 'org.apache.aries.blueprint' from resources 
 org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.3] and 
 org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.3] via 
 two dependency chains.
 Chain 1:
   org.apache.activemq.activemq-blueprint 
 [org.apache.activemq.activemq-blueprint/5.11.1]
 import: 
 ((osgi.wiring.package=org.apache.aries.blueprint)(version=1.0.0)(!(version=2.0.0)))
  |
 export: osgi.wiring.package: org.apache.aries.blueprint
   org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.3]
 Chain 2:
   org.apache.activemq.activemq-blueprint 
 [org.apache.activemq.activemq-blueprint/5.11.1]
 import: 
 ((osgi.wiring.package=org.apache.xbean.blueprint.context.impl)(version=3.13.0)(!(version=4.0.0)))
  |
 export: osgi.wiring.package=org.apache.xbean.blueprint.context.impl; 
 uses:=org.apache.aries.blueprint
   org.apache.xbean.blueprint [org.apache.xbean.blueprint/3.18.0]
 import: 
 ((osgi.wiring.package=org.apache.aries.blueprint)(version=1.0.0)(!(version=2.0.0)))
  |
 export: osgi.wiring.package: org.apache.aries.blueprint
   org.apache.aries.blueprint.core [org.apache.aries.blueprint.core/1.4.3]
   at 
 org.apache.felix.resolver.ResolverImpl.checkDynamicPackageSpaceConsistency(ResolverImpl.java:1410)[org.apache.felix.framework-5.0.0.jar:]
   at 
 org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1190)[org.apache.felix.framework-5.0.0.jar:]
   at 
 org.apache.felix.resolver.ResolverImpl.checkDynamicPackageSpaceConsistency(ResolverImpl.java:1502)[org.apache.felix.framework-5.0.0.jar:]
   at 
 org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1190)[org.apache.felix.framework-5.0.0.jar:]
   at 
 org.apache.felix.resolver.ResolverImpl.checkDynamicPackageSpaceConsistency(ResolverImpl.java:1502)[org.apache.felix.framework-5.0.0.jar:]
   at 
 org.apache.felix.resolver.ResolverImpl.checkPackageSpaceConsistency(ResolverImpl.java:1190)[org.apache.felix.framework-5.0.0.jar:]
   at 
 org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:289)[org.apache.felix.framework-5.0.0.jar:]
   at 
 org.apache.karaf.features.internal.region.SubsystemResolver.resolve(SubsystemResolver.java:185)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
   at 
 org.apache.karaf.features.internal.service.Deployer.deploy(Deployer.java:261)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
   at 
 org.apache.karaf.features.internal.service.FeaturesServiceImpl.doProvision(FeaturesServiceImpl.java:1061)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
   at 
 org.apache.karaf.features.internal.service.FeaturesServiceImpl$1.call(FeaturesServiceImpl.java:960)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
   at java.util.concurrent.FutureTask.run(FutureTask.java:266)[:1.8.0_31]
   at 
 java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_31]
   at 
 java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_31]
   at java.lang.Thread.run(Thread.java:745)[:1.8.0_31]
 {code}
 The behaviour is not predictable. Installation worked x times, afterwards 
 installation failed y times so you may need some trys to reproduce.
 To reproduce execute:
 {code}
 feature:repo-add activemq 5.11.1
 feature:install activemq-blueprint
 {code}
 if you don't get the exception stop the container, delete data folder and try 
 again.



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

[jira] [Commented] (KARAF-3663) Unable to deploy KAR

2015-05-29 Thread Alexey Markevich (JIRA) 

[ 
https://issues.apache.org/jira/browse/KARAF-3663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14564603#comment-14564603
 ] 

Alexey Markevich commented on KARAF-3663:
-

Finally I found a problem: test-0.1-feature.xml name is wrong; using 
test-feature-0.1.xml all works fine

 Unable to deploy KAR
 

 Key: KARAF-3663
 URL: https://issues.apache.org/jira/browse/KARAF-3663
 Project: Karaf
  Issue Type: Bug
  Components: karaf-kar
Affects Versions: 4.0.0.M3
Reporter: Alexey Markevich
Assignee: Jean-Baptiste Onofré
 Fix For: 4.0.0.M3

 Attachments: test-0.1.kar


 {noformat}
 2015-04-14 10:21:43,635 | WARN  | -SNAPSHOT/deploy | KarServiceImpl   
 | 34 - org.apache.karaf.kar.core - 4.0.0.SNAPSHOT | Unable to add 
 repository 'test/test-feature/0.1/test-0.1-feature.xml'
 java.io.IOException: URI is not absolute : 
 test/test-feature/0.1/test-0.1-feature.xml
   at 
 org.apache.karaf.features.internal.service.RepositoryImpl.load(RepositoryImpl.java:85)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
   at 
 org.apache.karaf.features.internal.service.FeaturesServiceImpl.loadRepository(FeaturesServiceImpl.java:379)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
   at 
 org.apache.karaf.features.internal.service.FeaturesServiceImpl.addRepository(FeaturesServiceImpl.java:399)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
   at 
 org.apache.karaf.features.internal.service.FeaturesServiceImpl.addRepository(FeaturesServiceImpl.java:390)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
   at 
 org.apache.karaf.kar.internal.KarServiceImpl.addToFeaturesRepositories(KarServiceImpl.java:193)[34:org.apache.karaf.kar.core:4.0.0.SNAPSHOT]
   at 
 org.apache.karaf.kar.internal.KarServiceImpl.install(KarServiceImpl.java:94)[34:org.apache.karaf.kar.core:4.0.0.SNAPSHOT]
   at 
 org.apache.karaf.kar.internal.KarServiceImpl.install(KarServiceImpl.java:85)[34:org.apache.karaf.kar.core:4.0.0.SNAPSHOT]
   at 
 org.apache.karaf.deployer.kar.KarArtifactInstaller.install(KarArtifactInstaller.java:50)[25:org.apache.karaf.deployer.kar:4.0.0.SNAPSHOT]
   at 
 org.apache.felix.fileinstall.internal.DirectoryWatcher.install(DirectoryWatcher.java:931)[4:org.apache.felix.fileinstall:3.5.0]
   at 
 org.apache.felix.fileinstall.internal.DirectoryWatcher.install(DirectoryWatcher.java:865)[4:org.apache.felix.fileinstall:3.5.0]
   at 
 org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:482)[4:org.apache.felix.fileinstall:3.5.0]
   at 
 org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:358)[4:org.apache.felix.fileinstall:3.5.0]
   at 
 org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:310)[4:org.apache.felix.fileinstall:3.5.0]
 Caused by: java.lang.IllegalArgumentException: URI is not absolute
   at java.net.URI.toURL(URI.java:1095)[:1.7.0_76]
   at 
 org.apache.karaf.features.internal.service.RepositoryImpl.load(RepositoryImpl.java:80)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
   ... 12 more
 {noformat}



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

[jira] [Commented] (KARAF-3663) Unable to deploy KAR

2015-05-29 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/KARAF-3663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14564773#comment-14564773
 ] 

Jean-Baptiste Onofré commented on KARAF-3663:
-

I guess that the problem is in your feature XML. Do you mind if I fix this Jira 
as Not A Problem ? Thanks.

 Unable to deploy KAR
 

 Key: KARAF-3663
 URL: https://issues.apache.org/jira/browse/KARAF-3663
 Project: Karaf
  Issue Type: Bug
  Components: karaf-kar
Affects Versions: 4.0.0.M3
Reporter: Alexey Markevich
Assignee: Jean-Baptiste Onofré
 Fix For: 4.0.0.M3

 Attachments: test-0.1.kar


 {noformat}
 2015-04-14 10:21:43,635 | WARN  | -SNAPSHOT/deploy | KarServiceImpl   
 | 34 - org.apache.karaf.kar.core - 4.0.0.SNAPSHOT | Unable to add 
 repository 'test/test-feature/0.1/test-0.1-feature.xml'
 java.io.IOException: URI is not absolute : 
 test/test-feature/0.1/test-0.1-feature.xml
   at 
 org.apache.karaf.features.internal.service.RepositoryImpl.load(RepositoryImpl.java:85)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
   at 
 org.apache.karaf.features.internal.service.FeaturesServiceImpl.loadRepository(FeaturesServiceImpl.java:379)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
   at 
 org.apache.karaf.features.internal.service.FeaturesServiceImpl.addRepository(FeaturesServiceImpl.java:399)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
   at 
 org.apache.karaf.features.internal.service.FeaturesServiceImpl.addRepository(FeaturesServiceImpl.java:390)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
   at 
 org.apache.karaf.kar.internal.KarServiceImpl.addToFeaturesRepositories(KarServiceImpl.java:193)[34:org.apache.karaf.kar.core:4.0.0.SNAPSHOT]
   at 
 org.apache.karaf.kar.internal.KarServiceImpl.install(KarServiceImpl.java:94)[34:org.apache.karaf.kar.core:4.0.0.SNAPSHOT]
   at 
 org.apache.karaf.kar.internal.KarServiceImpl.install(KarServiceImpl.java:85)[34:org.apache.karaf.kar.core:4.0.0.SNAPSHOT]
   at 
 org.apache.karaf.deployer.kar.KarArtifactInstaller.install(KarArtifactInstaller.java:50)[25:org.apache.karaf.deployer.kar:4.0.0.SNAPSHOT]
   at 
 org.apache.felix.fileinstall.internal.DirectoryWatcher.install(DirectoryWatcher.java:931)[4:org.apache.felix.fileinstall:3.5.0]
   at 
 org.apache.felix.fileinstall.internal.DirectoryWatcher.install(DirectoryWatcher.java:865)[4:org.apache.felix.fileinstall:3.5.0]
   at 
 org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:482)[4:org.apache.felix.fileinstall:3.5.0]
   at 
 org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:358)[4:org.apache.felix.fileinstall:3.5.0]
   at 
 org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:310)[4:org.apache.felix.fileinstall:3.5.0]
 Caused by: java.lang.IllegalArgumentException: URI is not absolute
   at java.net.URI.toURL(URI.java:1095)[:1.7.0_76]
   at 
 org.apache.karaf.features.internal.service.RepositoryImpl.load(RepositoryImpl.java:80)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
   ... 12 more
 {noformat}



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

[jira] [Commented] (KARAF-3663) Unable to deploy KAR

2015-05-29 Thread Alexey Markevich (JIRA) 

[ 
https://issues.apache.org/jira/browse/KARAF-3663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14564786#comment-14564786
 ] 

Alexey Markevich commented on KARAF-3663:
-

Ok. FYI this case works fine in karaf 2.x

 Unable to deploy KAR
 

 Key: KARAF-3663
 URL: https://issues.apache.org/jira/browse/KARAF-3663
 Project: Karaf
  Issue Type: Bug
  Components: karaf-kar
Affects Versions: 4.0.0.M3
Reporter: Alexey Markevich
Assignee: Jean-Baptiste Onofré
 Fix For: 4.0.0.M3

 Attachments: test-0.1.kar


 {noformat}
 2015-04-14 10:21:43,635 | WARN  | -SNAPSHOT/deploy | KarServiceImpl   
 | 34 - org.apache.karaf.kar.core - 4.0.0.SNAPSHOT | Unable to add 
 repository 'test/test-feature/0.1/test-0.1-feature.xml'
 java.io.IOException: URI is not absolute : 
 test/test-feature/0.1/test-0.1-feature.xml
   at 
 org.apache.karaf.features.internal.service.RepositoryImpl.load(RepositoryImpl.java:85)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
   at 
 org.apache.karaf.features.internal.service.FeaturesServiceImpl.loadRepository(FeaturesServiceImpl.java:379)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
   at 
 org.apache.karaf.features.internal.service.FeaturesServiceImpl.addRepository(FeaturesServiceImpl.java:399)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
   at 
 org.apache.karaf.features.internal.service.FeaturesServiceImpl.addRepository(FeaturesServiceImpl.java:390)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
   at 
 org.apache.karaf.kar.internal.KarServiceImpl.addToFeaturesRepositories(KarServiceImpl.java:193)[34:org.apache.karaf.kar.core:4.0.0.SNAPSHOT]
   at 
 org.apache.karaf.kar.internal.KarServiceImpl.install(KarServiceImpl.java:94)[34:org.apache.karaf.kar.core:4.0.0.SNAPSHOT]
   at 
 org.apache.karaf.kar.internal.KarServiceImpl.install(KarServiceImpl.java:85)[34:org.apache.karaf.kar.core:4.0.0.SNAPSHOT]
   at 
 org.apache.karaf.deployer.kar.KarArtifactInstaller.install(KarArtifactInstaller.java:50)[25:org.apache.karaf.deployer.kar:4.0.0.SNAPSHOT]
   at 
 org.apache.felix.fileinstall.internal.DirectoryWatcher.install(DirectoryWatcher.java:931)[4:org.apache.felix.fileinstall:3.5.0]
   at 
 org.apache.felix.fileinstall.internal.DirectoryWatcher.install(DirectoryWatcher.java:865)[4:org.apache.felix.fileinstall:3.5.0]
   at 
 org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:482)[4:org.apache.felix.fileinstall:3.5.0]
   at 
 org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:358)[4:org.apache.felix.fileinstall:3.5.0]
   at 
 org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:310)[4:org.apache.felix.fileinstall:3.5.0]
 Caused by: java.lang.IllegalArgumentException: URI is not absolute
   at java.net.URI.toURL(URI.java:1095)[:1.7.0_76]
   at 
 org.apache.karaf.features.internal.service.RepositoryImpl.load(RepositoryImpl.java:80)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
   ... 12 more
 {noformat}



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

[jira] [Commented] (KARAF-3663) Unable to deploy KAR

2015-05-29 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/KARAF-3663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14564791#comment-14564791
 ] 

Jean-Baptiste Onofré commented on KARAF-3663:
-

OK, I gonna check if the problem is in the features namespace used or in the 
deployer itself.

 Unable to deploy KAR
 

 Key: KARAF-3663
 URL: https://issues.apache.org/jira/browse/KARAF-3663
 Project: Karaf
  Issue Type: Bug
  Components: karaf-kar
Affects Versions: 4.0.0.M3
Reporter: Alexey Markevich
Assignee: Jean-Baptiste Onofré
 Fix For: 4.0.0.M3

 Attachments: test-0.1.kar


 {noformat}
 2015-04-14 10:21:43,635 | WARN  | -SNAPSHOT/deploy | KarServiceImpl   
 | 34 - org.apache.karaf.kar.core - 4.0.0.SNAPSHOT | Unable to add 
 repository 'test/test-feature/0.1/test-0.1-feature.xml'
 java.io.IOException: URI is not absolute : 
 test/test-feature/0.1/test-0.1-feature.xml
   at 
 org.apache.karaf.features.internal.service.RepositoryImpl.load(RepositoryImpl.java:85)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
   at 
 org.apache.karaf.features.internal.service.FeaturesServiceImpl.loadRepository(FeaturesServiceImpl.java:379)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
   at 
 org.apache.karaf.features.internal.service.FeaturesServiceImpl.addRepository(FeaturesServiceImpl.java:399)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
   at 
 org.apache.karaf.features.internal.service.FeaturesServiceImpl.addRepository(FeaturesServiceImpl.java:390)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
   at 
 org.apache.karaf.kar.internal.KarServiceImpl.addToFeaturesRepositories(KarServiceImpl.java:193)[34:org.apache.karaf.kar.core:4.0.0.SNAPSHOT]
   at 
 org.apache.karaf.kar.internal.KarServiceImpl.install(KarServiceImpl.java:94)[34:org.apache.karaf.kar.core:4.0.0.SNAPSHOT]
   at 
 org.apache.karaf.kar.internal.KarServiceImpl.install(KarServiceImpl.java:85)[34:org.apache.karaf.kar.core:4.0.0.SNAPSHOT]
   at 
 org.apache.karaf.deployer.kar.KarArtifactInstaller.install(KarArtifactInstaller.java:50)[25:org.apache.karaf.deployer.kar:4.0.0.SNAPSHOT]
   at 
 org.apache.felix.fileinstall.internal.DirectoryWatcher.install(DirectoryWatcher.java:931)[4:org.apache.felix.fileinstall:3.5.0]
   at 
 org.apache.felix.fileinstall.internal.DirectoryWatcher.install(DirectoryWatcher.java:865)[4:org.apache.felix.fileinstall:3.5.0]
   at 
 org.apache.felix.fileinstall.internal.DirectoryWatcher.doProcess(DirectoryWatcher.java:482)[4:org.apache.felix.fileinstall:3.5.0]
   at 
 org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:358)[4:org.apache.felix.fileinstall:3.5.0]
   at 
 org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:310)[4:org.apache.felix.fileinstall:3.5.0]
 Caused by: java.lang.IllegalArgumentException: URI is not absolute
   at java.net.URI.toURL(URI.java:1095)[:1.7.0_76]
   at 
 org.apache.karaf.features.internal.service.RepositoryImpl.load(RepositoryImpl.java:80)[6:org.apache.karaf.features.core:4.0.0.SNAPSHOT]
   ... 12 more
 {noformat}



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

[jira] [Resolved] (KARAF-3515) branding.properties file in the etc folder doesn't work

2015-05-29 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/KARAF-3515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré resolved KARAF-3515.
-
Resolution: Fixed

 branding.properties file in the etc folder doesn't work
 ---

 Key: KARAF-3515
 URL: https://issues.apache.org/jira/browse/KARAF-3515
 Project: Karaf
  Issue Type: Bug
  Components: karaf-shell
Affects Versions: 4.0.0.M1, 4.0.0.M2
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
 Fix For: 4.0.0.M3


 Dropping a branding.properties file in the etc folder doesn't work. The 
 default branding is used.



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

[jira] [Updated] (KARAF-3270) Add command/MBean operation to give current user and his roles

2015-05-29 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/KARAF-3270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-3270:

Fix Version/s: (was: 3.0.4)
   (was: 4.0.0.M3)
   3.0.5
   4.0.0

 Add command/MBean operation to give current user and his roles
 --

 Key: KARAF-3270
 URL: https://issues.apache.org/jira/browse/KARAF-3270
 Project: Karaf
  Issue Type: New Feature
  Components: karaf-shell
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
 Fix For: 4.0.0, 3.0.5


 When logged on with an user (on the local console, ssh, MBean), it would be 
 great to get the current username (even if we have in the prompt and in the 
 console session), but also with current user roles.



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

[jira] [Commented] (KARAF-3515) branding.properties file in the etc folder doesn't work

2015-05-29 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/KARAF-3515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14564788#comment-14564788
 ] 

Jean-Baptiste Onofré commented on KARAF-3515:
-

I tested and it works fine with latest 4.0.0-SNAPSHOT.

 branding.properties file in the etc folder doesn't work
 ---

 Key: KARAF-3515
 URL: https://issues.apache.org/jira/browse/KARAF-3515
 Project: Karaf
  Issue Type: Bug
  Components: karaf-shell
Affects Versions: 4.0.0.M1, 4.0.0.M2
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
 Fix For: 4.0.0.M3


 Dropping a branding.properties file in the etc folder doesn't work. The 
 default branding is used.



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

[jira] [Commented] (KARAF-3449) Incorrect serverName parsing in JDBC DataSource Blueprint

2015-05-29 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/KARAF-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14564847#comment-14564847
 ] 

Jean-Baptiste Onofré commented on KARAF-3449:
-

It's in the way and will be included in 3.0.4.

 Incorrect serverName parsing in JDBC DataSource Blueprint
 -

 Key: KARAF-3449
 URL: https://issues.apache.org/jira/browse/KARAF-3449
 Project: Karaf
  Issue Type: Bug
  Components: karaf-feature, karaf-osgi
Affects Versions: 3.0.2
Reporter: Justin Reock
Assignee: Jean-Baptiste Onofré
Priority: Minor
  Labels: features
 Fix For: 3.0.4, 4.0.0.M3, 2.4.3


 The serverName attribute in the JDBC DataSource code appears to be parsed 
 incorrectly.  It is tokenizing off of the ? character, but a trailing slash 
 exists between the database name and the ? parameter delimiter, so a request 
 for a database is matched against [database_name]/ as opposed to just 
 [database_name].  
 This may be isolated to just the PGPoolingDataSource for Postgres, I haven't 
 tried to replicate with another connection driver.  
 To demonstrate, set up a DataSource blueprint similar to the following:
 blueprint xmlns=http://www.osgi.org/xmlns/blueprint/v1.0.0;
   
bean id=dataSource class=org.postgresql.ds.PGPoolingDataSource 
 destroy-method=close
   property name=serverName value=localhost:5432/postgres/
   property name=user value=postgres/
   property name=password value=pgpassword/
   property name=dataSourceName value=pgConnectionPool/
   property name=initialConnections value=5/
   property name=maxConnections value=50 /
   /bean
   
   service interface=javax.sql.DataSource ref=dataSource
 service-properties
 entry key=osgi.jndi.service.name value=jdbc/postgres/
 /service-properties
   /service
 /blueprint
 ---
 Note that the intended database name from the serverName string here is 
 postgres.  Upon attempting jdbc actions, the following error message will 
 be returned from the DataSource:
 2015-01-16 16:22:32,398 | ERROR | h for user karaf | JdbcServiceImpl  
 | 119 - org.apache.karaf.jdbc.core - 3.0.2 | Can't get information 
 about datasource jdbc/postgres
 org.postgresql.util.PSQLException: FATAL: database postgres/ does not exist
 Notice the trailing slash after the database name.  That's because the 
 qualified URL for the database is:
 jdbc:postgresql://localhost:5432:postgres/?loginTimeout=0socketTimeout=0prepareThreshold=5unknownLength=2147483647tcpKeepAlive=falsebinaryTransfer=truedisableColumnSanitiser=false
 The trailing slash is coming in because the qualified name is being parsed 
 using the ? as a delimiter.  This is provable, because the following 
 serverName property can be used as a workaround:
  property name=serverName value=localhost:5432/postgres?/
 Note the ? at the end of the value.  This forces the interpreter to parse the 
 proper database name.  So the fix here would be either to account for the 
 trailing slash in the qualified name, or, not to append the slash at all when 
 deriving the qualified name.



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

[jira] [Updated] (KARAF-969) Feature installer should not accept different features with equal names

2015-05-29 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/KARAF-969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-969:
---
Fix Version/s: (was: 4.0.0.M3)
   4.0.0

 Feature installer should not accept different features with equal names
 ---

 Key: KARAF-969
 URL: https://issues.apache.org/jira/browse/KARAF-969
 Project: Karaf
  Issue Type: Bug
  Components: karaf-feature
Affects Versions: 2.2.2
Reporter: Geert Schuring
  Labels: duplicate, features, name, namespaces
 Fix For: 4.0.0, 2.4.3, 3.0.5


 The feature installer should reject feature files that contain features with 
 conflicting names. The installer currently allows this, while the install 
 command cannot differentiate between two features with the same name.
 Maybe the concept of feature namespaces would be a good solution. The feature 
 repository name could function as the namespace. The install command should 
 then support something like this:
 {code}
 features:install repo:feature
 {code}



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

[jira] [Created] (KARAF-3749) Add support for JBoss Transaction

2015-05-29 Thread Susan Javurek (JIRA) 
Susan Javurek created KARAF-3749:


 Summary: Add support for JBoss Transaction
 Key: KARAF-3749
 URL: https://issues.apache.org/jira/browse/KARAF-3749
 Project: Karaf
  Issue Type: New Feature
Reporter: Susan Javurek


There's increased demand to use this transaction manager and we'd like to 
explore linking it into karaf.



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

[jira] [Updated] (KARAF-3749) Add support for JBoss Transaction Manager

2015-05-29 Thread Susan Javurek (JIRA) 

 [ 
https://issues.apache.org/jira/browse/KARAF-3749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Susan Javurek updated KARAF-3749:
-
Summary: Add support for JBoss Transaction Manager  (was: Add support for 
JBoss Transaction)

 Add support for JBoss Transaction Manager
 -

 Key: KARAF-3749
 URL: https://issues.apache.org/jira/browse/KARAF-3749
 Project: Karaf
  Issue Type: New Feature
Reporter: Susan Javurek

 There's increased demand to use this transaction manager and we'd like to 
 explore linking it into karaf.



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

[jira] [Updated] (KARAF-2140) Add an explicit allowEmptyPasswords to the LDAPLoginModule defaulting to false

2015-05-29 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/KARAF-2140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-2140:

Fix Version/s: (was: 4.0.0.M3)
   4.0.0

 Add an explicit allowEmptyPasswords to the LDAPLoginModule defaulting to false
 --

 Key: KARAF-2140
 URL: https://issues.apache.org/jira/browse/KARAF-2140
 Project: Karaf
  Issue Type: Improvement
  Components: karaf-core
Reporter: Guillaume Nodet
Assignee: Jean-Baptiste Onofré
 Fix For: 4.0.0, 2.4.3, 3.0.5


 LDAP servers usually allow anonymous identification by sending an empty 
 passwords.  The roles checks should guard against this, but a specific option 
 would close any risk.



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

[jira] [Updated] (KARAF-1006) Port current kittests to newly added integration test framework

2015-05-29 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/KARAF-1006?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-1006:

Fix Version/s: (was: 4.0.0.M3)

 Port current kittests to newly added integration test framework
 ---

 Key: KARAF-1006
 URL: https://issues.apache.org/jira/browse/KARAF-1006
 Project: Karaf
  Issue Type: Improvement
  Components: karaf-test
Reporter: Andreas Pieber
Assignee: Andreas Pieber

 The current kit tests are almost done entirely manually. The new test 
 framework though comes with a native runner which can do the same as the 
 current framework but with ways less code.



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

[jira] [Updated] (KARAF-1043) Allow @Option and @Argument on method

2015-05-29 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/KARAF-1043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-1043:

Fix Version/s: (was: 4.0.0.M3)

 Allow @Option and @Argument on method
 -

 Key: KARAF-1043
 URL: https://issues.apache.org/jira/browse/KARAF-1043
 Project: Karaf
  Issue Type: Improvement
  Components: karaf-shell
Reporter: Jean-Baptiste Onofré

 Currently, @Option and @Argument annotations are allowed for attributes. I 
 could be interesting (for validation for instance) to have it on methods.



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

[jira] [Updated] (KARAF-1952) Allow Karaf monitoring using host:port

2015-05-29 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/KARAF-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-1952:

Fix Version/s: (was: 4.0.0.M3)
   4.0.0

 Allow Karaf monitoring using host:port
 --

 Key: KARAF-1952
 URL: https://issues.apache.org/jira/browse/KARAF-1952
 Project: Karaf
  Issue Type: Improvement
  Components: karaf-core
Reporter: Jean-Baptiste Onofré
Assignee: Jean-Baptiste Onofré
 Fix For: 4.0.0, 2.4.3, 3.0.5


 Currently, to be able to monitore Karaf (for instance in jconsole), we have 
 to use the service URL looking like:
 service:rmi:jmx:///://hostname:port/karaf-root
 To simplify the monitoring, it would be great to support directly 
 hostname:port.



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

[jira] [Updated] (KARAF-1897) Use dynamic port allocation of integration tests

2015-05-29 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/KARAF-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-1897:

Fix Version/s: (was: 4.0.0.M3)

 Use dynamic port allocation of integration tests
 

 Key: KARAF-1897
 URL: https://issues.apache.org/jira/browse/KARAF-1897
 Project: Karaf
  Issue Type: Test
  Components: karaf-test
Affects Versions: 3.0.0
Reporter: Christian Schneider

 Currently the ports of the integration tests are the same as in a default 
 karaf installation. So it is impossible to run a karaf and also run a build 
 on the same machine. 
 So the easiest solution is to change the ports to new numbers. Additionally 
 it would be good to use dynamic free ports so even two builds can run at the 
 same time.



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

[jira] [Updated] (KARAF-2266) Warn and override when feature can not install files

2015-05-29 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/KARAF-2266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-2266:

Fix Version/s: (was: 4.0.0.M3)
   3.0.5
   4.0.0

 Warn and override when feature can not install files
 

 Key: KARAF-2266
 URL: https://issues.apache.org/jira/browse/KARAF-2266
 Project: Karaf
  Issue Type: Improvement
  Components: karaf-feature
Affects Versions: 3.0.0.RC1
Reporter: Christian Schneider
Assignee: Jean-Baptiste Onofré
 Fix For: 4.0.0, 3.0.5


 karaf can deploy files like config files during the installation of a 
 feature. If the file is already present then it is not overwritten.
 I wonder if we should print a warning in this case. One use case for this is 
 a new version of a feature that adds a new needed property
 to a config file. If the old feature was already present then the old config 
 will be present and the user may also have done changes.
 So there might be cases where a feature works if it can install its default 
 configs but does not work when they are already present but invalid.
 So we could write for each file that is already present:
 Warning: file path to be deployed is already present and will not be 
 changed.
 We could also provide an option in feature:install like -f that forces all 
 files to be overwritten if someone wants to make sure the feature 
 installation should use the defaults. 



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

[jira] [Updated] (KARAF-2382) Add a command to show bundles with split packages

2015-05-29 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/KARAF-2382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-2382:

Fix Version/s: (was: 4.0.0.M3)
   4.0.0

 Add a command to show bundles with split packages
 -

 Key: KARAF-2382
 URL: https://issues.apache.org/jira/browse/KARAF-2382
 Project: Karaf
  Issue Type: New Feature
  Components: karaf-shell
Reporter: Jean-Baptiste Onofré
 Fix For: 4.0.0, 2.4.3, 3.0.5






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

[jira] [Updated] (KARAF-2011) dev:watch looks in an incorrect local maven repository

2015-05-29 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/KARAF-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-2011:

Fix Version/s: (was: 4.0.0.M3)
   4.0.0

 dev:watch looks in an incorrect local maven repository
 --

 Key: KARAF-2011
 URL: https://issues.apache.org/jira/browse/KARAF-2011
 Project: Karaf
  Issue Type: Bug
  Components: karaf-shell
Affects Versions: 2.2.9, 2.3.0
Reporter: Bengt Rodehav
Assignee: Jean-Baptiste Onofré
Priority: Minor
 Fix For: 4.0.0, 2.4.3, 3.0.5


 If a non-default maven repository is used (by setting the localRepository 
 property in maven's settings.xml), then dev:watch does not work. It seems 
 like dev:watch does not consider the localRepository setting when looking 
 for a bundle in maven.
 Note that other parts of Karaf does take the localRepository setting into 
 account since installing features and using the update command works.
 This has been discussed on the user mailing list:
 http://karaf.922171.n3.nabble.com/dev-watch-problems-td4026725.html#a4026730



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

[jira] [Updated] (KARAF-2219) Add option to jaas LoginModules to skip checking the credentials

2015-05-29 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/KARAF-2219?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré updated KARAF-2219:

Fix Version/s: (was: 4.0.0.M3)

 Add option to jaas LoginModules to skip checking the credentials
 

 Key: KARAF-2219
 URL: https://issues.apache.org/jira/browse/KARAF-2219
 Project: Karaf
  Issue Type: Improvement
  Components: karaf-core
Affects Versions: 3.0.0
Reporter: Christian Schneider

 In some cases the user is already authenticated in some other way and a JAAS 
 LoginModule should only retrieve the roles of a user. 
 For this case it makes sense to introduce an option like checkCredentials 
 or authenticate with default to true. If it is set to false in a jaas realm 
 module config then the credentials should not be validated.



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

[jira] [Created] (KARAF-3750) cellar:config, cellar:bundle, cellar:feature bundles failing on child nodes of apache servicemix 5.3.2

2015-05-29 Thread Manohar Gandra (JIRA) 
Manohar Gandra created KARAF-3750:
-

 Summary: cellar:config, cellar:bundle, cellar:feature bundles 
failing on child nodes of apache servicemix 5.3.2
 Key: KARAF-3750
 URL: https://issues.apache.org/jira/browse/KARAF-3750
 Project: Karaf
  Issue Type: Bug
  Components: cellar-bundle, cellar-config, cellar-features
Affects Versions: cellar-2.3.6
 Environment: CentOS 6.6
Reporter: Manohar Gandra
Priority: Critical


We have create 3 child nodes for apache-servicemix-5.3.2. Installed 
cellar-2.3.6 on root node and all the child nodes. 

We also created a new cluster group (other than default) and joined all the 3 
child nodes in this group. Root node is excluded from this group. 

cluster:group-create group name  (this command on root node)
cluster:group-join group name (this command run on 3 child nodes).

All the 3 nodes successfully joined in cluster group.

After joining the group, we have restarted the all the cluster members(root and 
child nodes). We see Cellar:feature, cellar:config and cellar:bundle bundles in 
failed state in child nodes.

 206] [Active ] [Failure ] [   ] [   40] Apache Karaf :: Cellar :: 
Config (2.3.6)
[ 207] [Active ] [Failure ] [   ] [   40] Apache Karaf :: Cellar :: 
Bundle (2.3.6)
[ 208] [Active ] [Failure ] [   ] [   40] Apache Karaf :: Cellar :: 
Features (2.3.6)

We are seeing following error in logs.

2015-05-29 10:31:21,507 | ERROR | rint Extender: 1 | BlueprintContainerImpl 
  | ?   ? | 14 - 
org.apache.aries.blueprint.core - 1.4.2 | Unable to start blueprint container 
for bundle org.apache.karaf.cellar.features
org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to 
initialize bean synchronizer
at 
org.apache.aries.blueprint.container.BeanRecipe.runBeanProcInit(BeanRecipe.java:714)[14:org.apache.aries.blueprint.core:1.4.2]
at 
org.apache.aries.blueprint.container.BeanRecipe.internalCreate2(BeanRecipe.java:824)[14:org.apache.aries.blueprint.core:1.4.2]
at 
org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:787)[14:org.apache.aries.blueprint.core:1.4.2]
at 
org.apache.aries.blueprint.di.AbstractRecipe$1.call(AbstractRecipe.java:79)[14:org.apache.aries.blueprint.core:1.4.2]
at 
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)[:1.6.0_34]
at java.util.concurrent.FutureTask.run(FutureTask.java:166)[:1.6.0_34]
at 
org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:88)[14:org.apache.aries.blueprint.core:1.4.2]
at 
org.apache.aries.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:245)[14:org.apache.aries.blueprint.core:1.4.2]
at 
org.apache.aries.blueprint.container.BlueprintRepository.createAll(BlueprintRepository.java:183)[14:org.apache.aries.blueprint.core:1.4.2]
at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:682)[14:org.apache.aries.blueprint.core:1.4.2]
at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:377)[14:org.apache.aries.blueprint.core:1.4.2]
at 
org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:269)[14:org.apache.aries.blueprint.core:1.4.2]
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)[:1.6.0_34]
at 
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)[:1.6.0_34]
at java.util.concurrent.FutureTask.run(FutureTask.java:166)[:1.6.0_34]
at 
org.apache.aries.blueprint.container.ExecutorServiceWrapper.run(ExecutorServiceWrapper.java:106)[14:org.apache.aries.blueprint.core:1.4.2]
at 
org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:48)[14:org.apache.aries.blueprint.core:1.4.2]
at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)[:1.6.0_34]
at 
java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)[:1.6.0_34]
at java.util.concurrent.FutureTask.run(FutureTask.java:166)[:1.6.0_34]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)[:1.6.0_34]
at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)[:1.6.0_34]
at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146)[:1.6.0_34]
at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)[:1.6.0_34]
at java.lang.Thread.run(Thread.java:701)[:1.6.0_34]
Caused by: java.lang.NullPointerException
at

[jira] [Assigned] (KARAF-3750) cellar:config, cellar:bundle, cellar:feature bundles failing on child nodes of apache servicemix 5.3.2

2015-05-29 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/KARAF-3750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jean-Baptiste Onofré reassigned KARAF-3750:
---

Assignee: Jean-Baptiste Onofré

 cellar:config, cellar:bundle, cellar:feature bundles failing on child nodes 
 of apache servicemix 5.3.2
 --

 Key: KARAF-3750
 URL: https://issues.apache.org/jira/browse/KARAF-3750
 Project: Karaf
  Issue Type: Bug
  Components: cellar-bundle, cellar-config, cellar-features
Affects Versions: cellar-2.3.6
 Environment: CentOS 6.6
Reporter: Manohar Gandra
Assignee: Jean-Baptiste Onofré
Priority: Critical

 We have create 3 child nodes for apache-servicemix-5.3.2. Installed 
 cellar-2.3.6 on root node and all the child nodes. 
 We also created a new cluster group (other than default) and joined all the 3 
 child nodes in this group. Root node is excluded from this group. 
 cluster:group-create group name  (this command on root node)
 cluster:group-join group name (this command run on 3 child nodes).
 All the 3 nodes successfully joined in cluster group.
 After joining the group, we have restarted the all the cluster members(root 
 and child nodes). We see Cellar:feature, cellar:config and cellar:bundle 
 bundles in failed state in child nodes.
  206] [Active ] [Failure ] [   ] [   40] Apache Karaf :: Cellar 
 :: Config (2.3.6)
 [ 207] [Active ] [Failure ] [   ] [   40] Apache Karaf :: Cellar 
 :: Bundle (2.3.6)
 [ 208] [Active ] [Failure ] [   ] [   40] Apache Karaf :: Cellar 
 :: Features (2.3.6)
 We are seeing following error in logs.
 2015-05-29 10:31:21,507 | ERROR | rint Extender: 1 | BlueprintContainerImpl   
 | ?   ? | 14 - 
 org.apache.aries.blueprint.core - 1.4.2 | Unable to start blueprint container 
 for bundle org.apache.karaf.cellar.features
 org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to 
 initialize bean synchronizer
   at 
 org.apache.aries.blueprint.container.BeanRecipe.runBeanProcInit(BeanRecipe.java:714)[14:org.apache.aries.blueprint.core:1.4.2]
   at 
 org.apache.aries.blueprint.container.BeanRecipe.internalCreate2(BeanRecipe.java:824)[14:org.apache.aries.blueprint.core:1.4.2]
   at 
 org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:787)[14:org.apache.aries.blueprint.core:1.4.2]
   at 
 org.apache.aries.blueprint.di.AbstractRecipe$1.call(AbstractRecipe.java:79)[14:org.apache.aries.blueprint.core:1.4.2]
   at 
 java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)[:1.6.0_34]
   at java.util.concurrent.FutureTask.run(FutureTask.java:166)[:1.6.0_34]
   at 
 org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:88)[14:org.apache.aries.blueprint.core:1.4.2]
   at 
 org.apache.aries.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:245)[14:org.apache.aries.blueprint.core:1.4.2]
   at 
 org.apache.aries.blueprint.container.BlueprintRepository.createAll(BlueprintRepository.java:183)[14:org.apache.aries.blueprint.core:1.4.2]
   at 
 org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:682)[14:org.apache.aries.blueprint.core:1.4.2]
   at 
 org.apache.aries.blueprint.container.BlueprintContainerImpl.doRun(BlueprintContainerImpl.java:377)[14:org.apache.aries.blueprint.core:1.4.2]
   at 
 org.apache.aries.blueprint.container.BlueprintContainerImpl.run(BlueprintContainerImpl.java:269)[14:org.apache.aries.blueprint.core:1.4.2]
   at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)[:1.6.0_34]
   at 
 java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)[:1.6.0_34]
   at java.util.concurrent.FutureTask.run(FutureTask.java:166)[:1.6.0_34]
   at 
 org.apache.aries.blueprint.container.ExecutorServiceWrapper.run(ExecutorServiceWrapper.java:106)[14:org.apache.aries.blueprint.core:1.4.2]
   at 
 org.apache.aries.blueprint.utils.threading.impl.DiscardableRunnable.run(DiscardableRunnable.java:48)[14:org.apache.aries.blueprint.core:1.4.2]
   at 
 java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)[:1.6.0_34]
   at 
 java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)[:1.6.0_34]
   at java.util.concurrent.FutureTask.run(FutureTask.java:166)[:1.6.0_34]
   at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:165)[:1.6.0_34]
   at 
 java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:266)[:1.6.0_34]
   at