questions about cellar2.32
Hi JB, I have question about cellar. I used karaf 2.3.3, cellar 2.3.2 below is got from the cellar introduction page. Distributed OSGi (optional): cellar-dosgi provides support of Distributed OSGi, allowing to call an OSGi service present on a remote node. *My question: I want to construct a distributed OSGI cluster. Do you have an simple example to demonstrate how does a client bundle in local call a service in remote node?* Thanks -- View this message in context: http://karaf.922171.n3.nabble.com/questions-about-cellar2-32-tp4031234.html Sent from the Karaf - User mailing list archive at Nabble.com.
Re: questions about cellar2.32
Hi, yes, I have an example ready (that I did for webinar). I will add it in the Cellar manual. Regards JB On 01/21/2014 12:49 PM, simafengyun1984 wrote: Hi JB, I have question about cellar. I used karaf 2.3.3, cellar 2.3.2 below is got from the cellar introduction page. Distributed OSGi (optional): cellar-dosgi provides support of Distributed OSGi, allowing to call an OSGi service present on a remote node. *My question: I want to construct a distributed OSGI cluster. Do you have an simple example to demonstrate how does a client bundle in local call a service in remote node?* Thanks -- View this message in context: http://karaf.922171.n3.nabble.com/questions-about-cellar2-32-tp4031234.html Sent from the Karaf - User mailing list archive at Nabble.com. -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
Re: Problems with webconsole and bundle cache
@jb webconsole: I'm not sure i understand you correctly. If i edit the location of webconsole in the org.apache.karaf.feaures.cfg, it changes nothing. I have the same problem, it does not matter if webconsole is at the beginning of featuresBoot, at the middle or at the end. Should I edit the standard-3.0.0-features.xml? Sorry if this question is really stupid :). featuresBootAsynchonous is set to false. bundle cache: switching the framework container to equinox seems to help. I ran a couple of test, trying manual file install via the bundle:install file://- command and installing bundles via the deploy folder, which worked with equinox and did not with felix, error was always like this: ERROR: Error reloading cached bundle, removing it: /srv/karaf-3.0.0/data/cache/bundle135 (java.lang.NullPointerException) java.lang.NullPointerException at org.apache.felix.framework.cache.BundleArchive.createRevisionFromLocation(BundleArchive.java:869) at org.apache.felix.framework.cache.BundleArchive.reviseInternal(BundleArchive.java:550) at org.apache.felix.framework.cache.BundleArchive.init(BundleArchive.java:226) at org.apache.felix.framework.cache.BundleCache.getArchives(BundleCache.java:247) at org.apache.felix.framework.Felix.init(Felix.java:705) at org.apache.karaf.main.Main.launch(Main.java:238) at org.apache.karaf.main.Main.main(Main.java:172) Like i said, using the deploy folder for bundle installation, i got the same results. Working with Equinox, not working with felix. I ran every test by force shutdown of the virtual machine on which karaf runs and manually starting karaf. I have not tested how things behave when using the service wrapper but will later today or tomorrow. After the forced shutdown i restarted the vm, and started karaf without clearing any cache. In between test i cleared the cache. Ace: I have just started with the provisioning part, and i'm not forced to use ACE. I got the idea from the book Enterprise OSGI in Action, and it sounded like exactly what i want: Provisioning and administering multiple targets from a central server. If there are better provisioning frameworks for my purpose I will try them out, thanks for your suggestions. I just thought since it is Apache, too, and kind of built for OSGi bundles, it seemed like a nice solution. I don't want something very complex, i have 1..n remote targets that should be provisioned with bundles from the same server. But i have to admit my knowledge about provisioning mechanisms in the OSGI World is very limited, i just wanted to try out and play around with the managementagent and the ace-server. For use in the production environment, I will have to spend a lot more time experimenting and upping my knowledge. The main problem is not the amount of bundles i want to provision, since for the foreseeable future, it will not be more than 5-10. But the amount of targets could become something in the hundreds, so if you have some more suggestions, I'm all open for it. @Achim: Seems Equinox works much better for me Regards Florin -- View this message in context: http://karaf.922171.n3.nabble.com/Problems-with-webconsole-and-bundle-cache-tp4031218p4031237.html Sent from the Karaf - User mailing list archive at Nabble.com.
Re: Problems with webconsole and bundle cache
Florin, thanks for the testing with equinox, I think we might have an issue with the felix framework then. regards, Achim 2014/1/21 F.Aubele florin.aub...@infraview.eu @jb webconsole: I'm not sure i understand you correctly. If i edit the location of webconsole in the org.apache.karaf.feaures.cfg, it changes nothing. I have the same problem, it does not matter if webconsole is at the beginning of featuresBoot, at the middle or at the end. Should I edit the standard-3.0.0-features.xml? Sorry if this question is really stupid :). featuresBootAsynchonous is set to false. bundle cache: switching the framework container to equinox seems to help. I ran a couple of test, trying manual file install via the bundle:install file://- command and installing bundles via the deploy folder, which worked with equinox and did not with felix, error was always like this: ERROR: Error reloading cached bundle, removing it: /srv/karaf-3.0.0/data/cache/bundle135 (java.lang.NullPointerException) java.lang.NullPointerException at org.apache.felix.framework.cache.BundleArchive.createRevisionFromLocation(BundleArchive.java:869) at org.apache.felix.framework.cache.BundleArchive.reviseInternal(BundleArchive.java:550) at org.apache.felix.framework.cache.BundleArchive.init(BundleArchive.java:226) at org.apache.felix.framework.cache.BundleCache.getArchives(BundleCache.java:247) at org.apache.felix.framework.Felix.init(Felix.java:705) at org.apache.karaf.main.Main.launch(Main.java:238) at org.apache.karaf.main.Main.main(Main.java:172) Like i said, using the deploy folder for bundle installation, i got the same results. Working with Equinox, not working with felix. I ran every test by force shutdown of the virtual machine on which karaf runs and manually starting karaf. I have not tested how things behave when using the service wrapper but will later today or tomorrow. After the forced shutdown i restarted the vm, and started karaf without clearing any cache. In between test i cleared the cache. Ace: I have just started with the provisioning part, and i'm not forced to use ACE. I got the idea from the book Enterprise OSGI in Action, and it sounded like exactly what i want: Provisioning and administering multiple targets from a central server. If there are better provisioning frameworks for my purpose I will try them out, thanks for your suggestions. I just thought since it is Apache, too, and kind of built for OSGi bundles, it seemed like a nice solution. I don't want something very complex, i have 1..n remote targets that should be provisioned with bundles from the same server. But i have to admit my knowledge about provisioning mechanisms in the OSGI World is very limited, i just wanted to try out and play around with the managementagent and the ace-server. For use in the production environment, I will have to spend a lot more time experimenting and upping my knowledge. The main problem is not the amount of bundles i want to provision, since for the foreseeable future, it will not be more than 5-10. But the amount of targets could become something in the hundreds, so if you have some more suggestions, I'm all open for it. @Achim: Seems Equinox works much better for me Regards Florin -- View this message in context: http://karaf.922171.n3.nabble.com/Problems-with-webconsole-and-bundle-cache-tp4031218p4031237.html Sent from the Karaf - User mailing list archive at Nabble.com. -- Apache Karaf http://karaf.apache.org/ Committer PMC OPS4J Pax Web http://wiki.ops4j.org/display/paxweb/Pax+Web/ Committer Project Lead OPS4J Pax for Vaadin http://team.ops4j.org/wiki/display/PAXVAADIN/Home Commiter Project Lead blog http://notizblog.nierbeck.de/
Re: Problems with webconsole and bundle cache
I agree. I know that a new Felix framework release is planned very soon. I will try to reproduce Florin's issue. Regards JB On 01/21/2014 03:28 PM, Achim Nierbeck wrote: Florin, thanks for the testing with equinox, I think we might have an issue with the felix framework then. regards, Achim 2014/1/21 F.Aubele florin.aub...@infraview.eu mailto:florin.aub...@infraview.eu @jb webconsole: I'm not sure i understand you correctly. If i edit the location of webconsole in the org.apache.karaf.feaures.cfg, it changes nothing. I have the same problem, it does not matter if webconsole is at the beginning of featuresBoot, at the middle or at the end. Should I edit the standard-3.0.0-features.xml? Sorry if this question is really stupid :). featuresBootAsynchonous is set to false. bundle cache: switching the framework container to equinox seems to help. I ran a couple of test, trying manual file install via the bundle:install file://- command and installing bundles via the deploy folder, which worked with equinox and did not with felix, error was always like this: ERROR: Error reloading cached bundle, removing it: /srv/karaf-3.0.0/data/cache/bundle135 (java.lang.NullPointerException) java.lang.NullPointerException at org.apache.felix.framework.cache.BundleArchive.createRevisionFromLocation(BundleArchive.java:869) at org.apache.felix.framework.cache.BundleArchive.reviseInternal(BundleArchive.java:550) at org.apache.felix.framework.cache.BundleArchive.init(BundleArchive.java:226) at org.apache.felix.framework.cache.BundleCache.getArchives(BundleCache.java:247) at org.apache.felix.framework.Felix.init(Felix.java:705) at org.apache.karaf.main.Main.launch(Main.java:238) at org.apache.karaf.main.Main.main(Main.java:172) Like i said, using the deploy folder for bundle installation, i got the same results. Working with Equinox, not working with felix. I ran every test by force shutdown of the virtual machine on which karaf runs and manually starting karaf. I have not tested how things behave when using the service wrapper but will later today or tomorrow. After the forced shutdown i restarted the vm, and started karaf without clearing any cache. In between test i cleared the cache. Ace: I have just started with the provisioning part, and i'm not forced to use ACE. I got the idea from the book Enterprise OSGI in Action, and it sounded like exactly what i want: Provisioning and administering multiple targets from a central server. If there are better provisioning frameworks for my purpose I will try them out, thanks for your suggestions. I just thought since it is Apache, too, and kind of built for OSGi bundles, it seemed like a nice solution. I don't want something very complex, i have 1..n remote targets that should be provisioned with bundles from the same server. But i have to admit my knowledge about provisioning mechanisms in the OSGI World is very limited, i just wanted to try out and play around with the managementagent and the ace-server. For use in the production environment, I will have to spend a lot more time experimenting and upping my knowledge. The main problem is not the amount of bundles i want to provision, since for the foreseeable future, it will not be more than 5-10. But the amount of targets could become something in the hundreds, so if you have some more suggestions, I'm all open for it. @Achim: Seems Equinox works much better for me Regards Florin -- View this message in context: http://karaf.922171.n3.nabble.com/Problems-with-webconsole-and-bundle-cache-tp4031218p4031237.html Sent from the Karaf - User mailing list archive at Nabble.com. -- Apache Karaf http://karaf.apache.org/ Committer PMC OPS4J Pax Web http://wiki.ops4j.org/display/paxweb/Pax+Web/ Committer Project Lead OPS4J Pax for Vaadin http://team.ops4j.org/wiki/display/PAXVAADIN/Home Commiter Project Lead blog http://notizblog.nierbeck.de/ -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
Re: AW: Schema for custom shell commands
Any further updates on this issue. I am using karaf 3.0.0 and facing the same issue. With namespace v1.1.0 and command element with about name attribute, getting following error. Caused by: org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to find a matching factory method getScope on class org.apache.karaf.shell.console.commands.NamespaceHandler for arguments [com.test.cmd.list] when instanciating bean #recipe-7 -- View this message in context: http://karaf.922171.n3.nabble.com/Schema-for-custom-shell-commands-tp4029047p4031242.html Sent from the Karaf - User mailing list archive at Nabble.com.
Re: AW: Schema for custom shell commands
Hi Vinu, I checked and if you use shell namespace 1.1.0, you have to NOT use the name attribute on the command element (the name is now taken from the command class). The name attribute is required only if you use shell namespace 1.0.0. However, namespace 1.0.0 is still supported in Karaf 3.0.0. Regards JB On 01/22/2014 07:26 AM, Vinu Raj wrote: Any further updates on this issue. I am using karaf 3.0.0 and facing the same issue. With namespace v1.1.0 and command element with about name attribute, getting following error. Caused by: org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to find a matching factory method getScope on class org.apache.karaf.shell.console.commands.NamespaceHandler for arguments [com.test.cmd.list] when instanciating bean #recipe-7 -- View this message in context: http://karaf.922171.n3.nabble.com/Schema-for-custom-shell-commands-tp4029047p4031242.html Sent from the Karaf - User mailing list archive at Nabble.com. -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
