Re: commons-logging needed for commons-configuration feature
I've only had this issue in cases, where an other plugin overwritten the MANIFEST.MF. -- *Ioannis Canellos* * ** Blog: http://iocanel.blogspot.com ** Twitter: iocanel *
Re: Question about Cellar distributed services
Second how would I create a jira? Never done it before. You need to go to that url: https://issues.apache.org/jira/browse/KARAF and click on create issue (requires registration). Then just fill in the form. -- *Ioannis Canellos* * ** Blog: http://iocanel.blogspot.com ** Twitter: iocanel *
Re: Question about Cellar distributed services
An NPE is definitely something we need to address. I am not sure if we should give more control to the client bundles for error handling, failover etc. But we definitely need to address this issue. Can you create a jira? -- *Ioannis Canellos* * ** Blog: http://iocanel.blogspot.com ** Twitter: iocanel *
Re: Configurable Command Completer
Hi Scott, The first thing you need to do is to acquire the command session in the completer. The command session can be acquired from the CommandSessionHolder which uses a thread local variable to store command sessions. From the command session you can get the argument list: ArgumentCompleter.ArgumentList list = (ArgumentCompleter.ArgumentList) commandSession.get(ArgumentCompleter.ARGUMENTS_LIST); A complete example is inside karaf itself at: https://svn.apache.org/repos/asf/karaf/trunk/config/command/src/main/java/org/apache/karaf/config/command/completers/ConfigurationPropertyCompleter.java I think that this should work on all karaf versions from 2.2.5 and above. -- *Ioannis Canellos* * FuseSource http://fusesource.com ** Blog: http://iocanel.blogspot.com ** Twitter: iocanel *
Re: Guidance on integrated testing solutions
Hi Tim, what pax-exam-karaf provides in addition to plain pax-exam testing, is that the test is run inside a real karaf container and you don't need to describe how you need the container itself to be provisioned. On top of that, it allows you to make use of all Karaf services from inside your test, including the features service itself which make provisioning of your application inside the integration test even more easy. In your test you can inject any OSGi service. You don't need to use karaf commands at all if you don't wish. But seeing how the executCommand method is implemented might help you understand how you can reuse OSGi services. I have some additional links to provide with automated itests using pax-exam-karaf: https://github.com/jclouds/jclouds-karaf/tree/master/itests https://svn.apache.org/repos/asf/whirr/trunk/platforms/karaf/itests/ https://github.com/fusesource/fuse/tree/master/fabric/fabric-itests/fabric-pax-exam Again, in those tests you'll see using the commands a lot, but that's more because I was trying to emulate use cases that reproduce bugs etc. Its not mandatory to do so. -- *Ioannis Canellos* * FuseSource http://fusesource.com ** Blog: http://iocanel.blogspot.com ** Twitter: iocanel *
Re: features autostart
I wish things like org.apache.karaf.features.core/FeaturesServiceImpl were broken into 10 small pieces with clear separation of concerns; I tried to have patch real fast, but afraid to mess up the 1500 lines blobs :-) Don't be afraid and give it a shot. The code isn't that big and it's quite easy to comprehend, I am sure you'll make it :-) -- *Ioannis Canellos* * FuseSource http://fusesource.com ** Blog: http://iocanel.blogspot.com ** Twitter: iocanel *
Re: Installing war support in Karaf 2.2.7
No, you don't seem to miss something. Inside a fresh karaf 2.2.7, features:list should display all available features icnluding war. Also features:listrepositories should work. Can you check if you accidentially removed any files from the default distribution? Extracting a fresh container would probably help. If you still have issues, please let us know about your os, java version etc. -- *Ioannis Canellos* * FuseSource http://fusesource.com ** Blog: http://iocanel.blogspot.com ** Twitter: iocanel *
Re: Error in stop script if KARAF_DEBUG is enabled
I haven't reviewed the patch, but I do like the idea, as I keep on having this issue myself all the time :) I don't see any reason why the stop script should run in debug mode, unless someone is debugging the stop itself. I'd say open a jira and attach the patch and we can continue the discussion from there. -- *Ioannis Canellos* * FuseSource http://fusesource.com ** Blog: http://iocanel.blogspot.com ** Twitter: iocanel *
Re: Karaf Cellar - Site Vs. Instance Configuration
I also see the configuration files I added to the etc directory (these are all config files for declarative service apps) are owned by bundle Apache Karaf :: Cellar :: Config. Is that correct? No, this is not correct! Cellar should not do that, as it can cause issues. Cellar should use *listConfigurations* instead of *getConfiguration* -- *Ioannis Canellos* * FuseSource http://fusesource.com ** Blog: http://iocanel.blogspot.com ** Twitter: iocanel *
Re: pax exam karaf framework with remote test containers
On a single machine you can create multiple karaf instances using the karaf admin service in order to test multiple karafs in a single host. If using the remote machines is a hard requirement, there are a few options for you out there, but they all require some additional effort. The idea would be to ssh into those machines from inside your test install start karaf and use it in your test. Some options on how to do it without having to code the world would be: a) Use jclouds-karaf with the byon provider (bring your own nodes) in order to be able to manage the remote machines. b) An other idea would be to use a project that I have been working on: Fuse Fabric http://fuse.fusesource.org/fabric/docs/getting-started.html. This will allow you among other to start Karaf instances on any host you have ssh access and easily manage it. Such test example: https://github.com/fusesource/fuse/blob/master/fabric/fabric-itests/fabric-pax-exam/src/test/java/org/fusesource/fabric/itests/paxexam/CreateSshAgentTest.java. Ioannis Canellos FuseSource Blog: http://iocanel.blogspot.com Apache Karaf Committer PMC Apache Camel Committer Apache ServiceMix Committer Apache Gora Committer Apache DirectMemory Committer
Re: About cluster:node-ping command in Cellar
Hi Xilai, The output is misleading, due to a bug. What actually happens is that all commands timeout after 10 seconds, but the ping command does not properly handle the timeout resulting in this false output. I think that this issue happens when pinging nodes on separate groups. Could you please file a jira about it? On 9 Φεβ 2012, at 12:25 μ.μ., Jean-Baptiste Onofré wrote: Hi Xilai, Some questions: - Which Cellar version ? - Which kind of discover used (static, unicast/multicast) ? If you do a system ping, what kind of latency do you have ? I tried on my VM without problem. Regards JB On 02/09/2012 10:52 AM, XiLai Dai wrote: Hi, When I try to run cluster:node-ping command with Karaf + Cellar cluster env, it always give a reply with about 10 seconds delay time if the target node is on the other machine. karaf@trun cluster:node-ping 192.168.2.104:5701 Pinging node 192.168.2.104:5701 PING 1 192.168.2.104:5701 10002ms PING 2 192.168.2.104:5701 10001ms PING 3 192.168.2.104:5701 10002ms PING 4 192.168.2.104:5701 1ms Is it Ok or any configuration need to be set? Or it's a known issue. Thanks! Regards. Xilai -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com Ioannis Canellos FuseSource Blog: http://iocanel.blogspot.com Apache Karaf Committer PMC Apache Camel Committer Apache ServiceMix Committer Apache Gora Committer Apache DirectMemory Committer
Re: karaf test framework: multiple test classes files in the same karaf instance
Hi Giacomo, I am not sure if this is possible. On 8 Φεβ 2012, at 6:30 μ.μ., Giacomo Coletta wrote: Hi, It’s sometime I’m using the karaf integration test framework and it works nicely. I usually run many tests in the same karaf instance. Up to now i only was able to properly configure, start karaf and run the tests in the same test class. Now the number of test is growing and i would like to put tests relating to different aspects in different classes, just to find them more easily, but anyway i would like not to have to configure and restart karaf several times, to save time. Any of you know how this could be done ? Thanks Giacomo Ioannis Canellos FuseSource Blog: http://iocanel.blogspot.com Apache Karaf Committer PMC Apache Camel Committer Apache ServiceMix Committer Apache Gora Committer Apache DirectMemory Committer
Re: Karaf, JPA and ConfigAdmin
I haven't tried it myself. Have you? It would be awsome if you could provide
some feedback about it.
On 19 Ιαν 2012, at 1:22 μ.μ., lbu wrote:
What about a blueprint configuration like the one below?
blueprint
xmlns=http://www.osgi.org/xmlns/blueprint/v1.0.0;
xmlns:jpa=http://aries.apache.org/xmlns/jpa/v1.1.0;
xmlns:cm=http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;
cm:property-placeholder persistent-id=my_object_id
cm:default-properties
cm:property name=jpa_param_1 value=A/
cm:property name=jpa_param_2 value=B/
/cm:default-properties
/cm:property-placeholder
bean id=my_object
jpa:context property=em unitname=unit_1 type=EXTENDED
map
entry key=jpa_param_1 value=${jpa_param_1} /
entry key=jpa_param_2 value=${jpa_param_1} /
/map
/jpa:context
/bean
/blueprint
--
View this message in context:
http://karaf.922171.n3.nabble.com/Karaf-JPA-and-ConfigAdmin-tp3667564p3672053.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Ioannis Canellos
FuseSource
Blog: http://iocanel.blogspot.com
Apache Karaf Committer PMC
Apache Camel Committer
Apache ServiceMix Committer
Apache Gora Committer
Apache DirectMemory Committer
Re: multiple ssh commands programatically
As of Karaf 2.2.5 you are able to specify the pid in all config commands as an option, which makes it easier to use from ssh. For example you can directly use something like this in a single command: config:propset --pid MyPID MyProperty MyValue On 10 Ιαν 2012, at 1:26 μ.μ., kmoens wrote: Tx for your reply. Found out that a simple line separator iso a space seperates different commands... In my case I create a StringBuilder with the different commands with the separator: sb.append(config:edit MyPID); sb.append(System.getProperty(line.separator)); sb.append(config:propset MyProperty MyValue); sb.append(System.getProperty(line.separator)); sb.append(config:update); and use this to create the ssh channel: channel = session.createChannel(exec, sb.toString()); -- View this message in context: http://karaf.922171.n3.nabble.com/multiple-ssh-commands-programatically-tp3644509p3647352.html Sent from the Karaf - User mailing list archive at Nabble.com. Ioannis Canellos FuseSource Blog: http://iocanel.blogspot.com Apache Karaf Committer PMC Apache Camel Committer Apache ServiceMix Committer Apache Gora Committer Apache DirectMemory Committer
Re: Costum distribution
From a first glance your approach looks sane to me. It reminds me
the service-mix packaging and it should work.
Now the problem you are having is that it can't find the felix jar. I see
that it tries to find the file right inside your distribution home, while
it should try to find it under the system folder.
i) Check that the file is properly located at : distro home under:
system/org/apache/felix/org.apache.felix.framework/3.0.9/org.apache.felix.framework-3.0.9.jar
ii) Check that in your system.properties file ${karaf.default.repository}
properly points to the system folder.
My guess is that you don't have a system.properties file at all and that
this is the root cause of all your problems.
Have fun!
--
*Ioannis Canellos*
*
FuseSource http://fusesource.com
**
Blog: http://iocanel.blogspot.com
**
Apache Karaf http://karaf.apache.org/ Committer PMC
Apache Camel http://camel.apache.org/ Committer
Apache ServiceMix http://servicemix.apache.org/ Committer
Apache Gora http://incubator.apache.org/gora/ Committer
Apache DirectMemory http://incubator.apache.org/directmemory/ Committer
*
Re: NoClassDefFoundError CommandProcessor/ not found by pax-exam-probe
By default your probe, will dynamically import all packages. All ? Well ... not all! Packages that are exported with provisional status will not be imported by default. You will have to modify your probe, like this: probe.setHeader(Constants.DYNAMICIMPORT_PACKAGE, *,org.apache.felix.service.*;status=provisional); And sorry for the late response ! -- *Ioannis Canellos* * FuseSource http://fusesource.com ** Blog: http://iocanel.blogspot.com ** Apache Karaf http://karaf.apache.org/ Committer PMC Apache Camel http://camel.apache.org/ Committer Apache ServiceMix http://servicemix.apache.org/ Committer Apache Gora http://incubator.apache.org/gora/ Committer Apache DirectMemory http://incubator.apache.org/directmemory/ Committer *
Re: Problem with starting web-app during startup
Hi Andi, You can have war feature and a bundle using the war protocol inside the same feature. The reason is that the war protocol is made available to the container once it is installed and will not be available at the time of the resolution. What you can do is to add the war feature in the boot features before your own feature. I think that this will work. -- *Ioannis Canellos* * FuseSource http://fusesource.com ** Blog: http://iocanel.blogspot.com ** Apache Karaf http://karaf.apache.org/ Committer PMC Apache ServiceMix http://servicemix.apache.org/ Committer Apache Gora http://incubator.apache.org/gora/ Committer *
Re: KARAF - SCA/Tuscany/ActiveMq binding example
Since you have no time, you can look at working examples at: http://code.google.com/p/camelinaction/source/browse/trunk/chapter7/jms/ The link above is a code sample from the Camel in Action book which is highly recommended. -- *Ioannis Canellos* * FuseSource http://fusesource.com ** Blog: http://iocanel.blogspot.com ** Apache Karaf http://karaf.apache.org/ Committer PMC Apache ServiceMix http://servicemix.apache.org/ Committer Apache Gora http://incubator.apache.org/gora/ Committer *
Re: Commons DBCP fails to install on Karaf 2.2.3
This mean that it cannot find javax.transaction package exported. You will need to install a bundle that provides it. You can try using this: osgi:install -s mvn:org.apache.geronimo.specs/geronimo-jta_1.1_spec/1.1.1 This will probably do the trick. -- *Ioannis Canellos* * FuseSource http://fusesource.com ** Blog: http://iocanel.blogspot.com ** Apache Karaf http://karaf.apache.org/ Committer PMC Apache ServiceMix http://servicemix.apache.org/ Committer Apache Gora http://incubator.apache.org/gora/ Committer *
Re: Features/bundles for OpenJPA/JTA
I think that the feature for jta is called transaction. -- *Ioannis Canellos* * FuseSource http://fusesource.com ** Blog: http://iocanel.blogspot.com ** Apache Karaf http://karaf.apache.org/ Committer PMC Apache ServiceMix http://servicemix.apache.org/ Committer Apache Gora http://incubator.apache.org/gora/ Committer *
Re: Commons DBCP fails to install on Karaf 2.2.3
You can also install the transaction feature of karaf, which will install the transaction api and aries transaction bundles. -- *Ioannis Canellos* * FuseSource http://fusesource.com ** Blog: http://iocanel.blogspot.com ** Apache Karaf http://karaf.apache.org/ Committer PMC Apache ServiceMix http://servicemix.apache.org/ Committer Apache Gora http://incubator.apache.org/gora/ Committer *
Re: Aries and Karaf
I recently made some enhancements on camel-jpa (upgraded to openjpa 2.1.1). Among the tests I did while working on that was to deploy a cut down version of the blog sample (a simpler project based on the blog sample) so that I can test the integration. It might help if you look at the bundles the camel-jpa is using. Not all of these are required just to run the blog sample, but you'll get a brief idea: https://svn.apache.org/repos/asf/camel/trunk/platforms/karaf/features/src/main/resources/features.xml You will also need jpa, transaction karaf featrues to be installed. I hope that it helps. -- *Ioannis Canellos* * FuseSource http://fusesource.com ** Blog: http://iocanel.blogspot.com ** Apache Karaf http://karaf.apache.org/ Committer PMC Apache ServiceMix http://servicemix.apache.org/ Committer Apache Gora http://incubator.apache.org/gora/ Committer *
Re: Adding Additional Cellar Map Configuration?
It should be ok now. -- *Ioannis Canellos* * FuseSource http://fusesource.com ** Blog: http://iocanel.blogspot.com ** Apache Karaf http://karaf.apache.org/ Committer PMC Apache ServiceMix http://servicemix.apache.org/ Committer Apache Gora http://incubator.apache.org/gora/ Committer *
Re: Cellar 2.2.2 Issues
Here is how it was supposed to work. When you add the repositories, the add repository event should be broadcasted to the other nodes of the group (as long as feature syncing on this group is enabled). The same should happen when you remove the url. It seems that that it works, for adding the repository, but doesn't work for removing the repository. This is why when you restart the node, it is pulling it back in. Could you add a jira for it? -- *Ioannis Canellos* * FuseSource http://fusesource.com ** Blog: http://iocanel.blogspot.com ** Apache Karaf http://karaf.apache.org/ Committer PMC Apache ServiceMix http://servicemix.apache.org/ Committer Apache Gora http://incubator.apache.org/gora/ Committer *
Re: Adding Additional Cellar Map Configuration?
If you could have a try on 842 that would be great. I think that you will have to build it yourself. Now regarding the custom datastore I think that the easiest way around would be to bundle it separately as hazelcast fragment in order to put it in the hazelcast.xml config. What we should do is to find a way to expose it as an OSGi service and somehow import that service when we create the Hazelcast configuration, but I am not sure if this should be solved in Cellar or Hazlecast itself. -- *Ioannis Canellos* * http://iocanel.blogspot.com Apache Karaf http://karaf.apache.org/ Committer PMC Apache ServiceMix http://servicemix.apache.org/ Committer Apache Gora http://incubator.apache.org/gora/ Committer *
Re: Configuring Cellar For TCP Instead Of Multicast
This was a bug that was introduced after implementing cloud discovery. If fixed it both on trunk and branch 2.2.x Here is the Jira: https://issues.apache.org/jira/browse/KARAF-856 -- *Ioannis Canellos* * http://iocanel.blogspot.com Apache Karaf http://karaf.apache.org/ Committer PMC Apache ServiceMix http://servicemix.apache.org/ Committer Apache Gora http://incubator.apache.org/gora/ Committer *
Re: Adding Additional Cellar Map Configuration?
The branch 2.2.x is now back to stable. On Wed, Sep 7, 2011 at 10:28 AM, Ioannis Canellos ioca...@gmail.com wrote: You will need to wait a bit before you try 842. The branch needs some more fixes. -- *Ioannis Canellos* * http://iocanel.blogspot.com Apache Karaf http://karaf.apache.org/ Committer PMC Apache ServiceMix http://servicemix.apache.org/ Committer Apache Gora http://incubator.apache.org/gora/ Committer * -- *Ioannis Canellos* * http://iocanel.blogspot.com Apache Karaf http://karaf.apache.org/ Committer PMC Apache ServiceMix http://servicemix.apache.org/ Committer Apache Gora http://incubator.apache.org/gora/ Committer * -- *Ioannis Canellos* * http://iocanel.blogspot.com Apache Karaf http://karaf.apache.org/ Committer PMC Apache ServiceMix http://servicemix.apache.org/ Committer Apache Gora http://incubator.apache.org/gora/ Committer *
Re: Configuring Cellar For TCP Instead Of Multicast
did you restart your Karaf instance after changing the Cellar configuration in etc file ? This is not necessary. Cellar should automatically get the configuration change event and restart the hazelcast instance. Garteth, have you also installed the cellar-cloud module? Its the only module that could add/remove tcpMemebers and what you are describing sounds like a bug in that module. -- *Ioannis Canellos* * http://iocanel.blogspot.com Apache Karaf http://karaf.apache.org/ Committer PMC Apache ServiceMix http://servicemix.apache.org/ Committer Apache Gora http://incubator.apache.org/gora/ Committer *
Re: Cellar And Hazelcast Questions
Hi Gareth, I think that it doesn't matter who initializes the instance. It matters though who creates the Hazelcast collection (Set,List,Map etc). So I think that the best approach is to reuse cellar's hazelcast instance which is exported as a service. I really don't understand why these scenarios fail for you. I reused the code you posted in your previous example and it worked fine (that was scenario 1). I've created a sample of a hazelcast application that reuses the cellar hazelcast instance (imports it as an OSGi service). You can have a look of that sample at: https://svn.apache.org/repos/asf/karaf/cellar/trunk/samples/hazelcast-app/. I wonder if the reason that makes this sample work is the fact that cellar-hazelcast has a dynamic-import on org.apache.karaf.cellar.* packages. I will try changing the package name and see if it still works. -- *Ioannis Canellos* * http://iocanel.blogspot.com Apache Karaf http://karaf.apache.org/ Committer PMC Apache ServiceMix http://servicemix.apache.org/ Committer Apache Gora http://incubator.apache.org/gora/ Committer *
Re: Cellar And Hazelcast Questions
Ok, I managed to reproduced it. I couldn't reproduce it so far because my sample bundle was dynamically imported by cellar-hazelcast bundle. I created a jira issue for that: https://issues.apache.org/jira/browse/KARAF-842 and I will start working on it. Till then you can either use a fragment or your own Hazelcast instance. Thanks Gareth for bringing this up and having the patience to try different scenarios/combinations. -- *Ioannis Canellos* * http://iocanel.blogspot.com Apache Karaf http://karaf.apache.org/ Committer PMC Apache ServiceMix http://servicemix.apache.org/ Committer Apache Gora http://incubator.apache.org/gora/ Committer *
Re: features.xml + dependency=true
Hi Sergey, The role of the dependency attribute is to mark that a bundle is a dependency. If a dependency is already satisfied (an existing bundle already exports the same packages/version) then it doesn't get installed. This behavior happens if the declared feature resolver is installed (e.g. obr is installed). In your case my-feature depends from the cxf feature. The cxf feature requires the presence of jdom, dom xstream etc. It specifies the servicemix bundles that satisfy those dependencies. If the specified resolver is present, it will check to see if those dependencies are already fulfilled and only in those case that are not, will those bundles be installed. I am not sure if the exception that you mentioned is somehow related to the dependency attribute. Maybe a complete stack trace could shed some more light into it. -- *Ioannis Canellos* * http://iocanel.blogspot.com Apache Karaf http://karaf.apache.org/ Committer PMC Apache ServiceMix http://servicemix.apache.org/ Committer Apache Gora http://incubator.apache.org/gora/ Committer *
Re: Pinging error
Issue created. https://issues.apache.org/ https://issues.apache.org/jira/browse/KARAF-839 jira/browse/KARAF-839 https://issues.apache.org/jira/browse/KARAF-839 * * On Sat, Aug 27, 2011 at 5:48 PM, Ioannis Canellos ioca...@gmail.com wrote: Even if the passed nodeId argument is wrong an NPE is not acceptable. I will raise an issue. -- *Ioannis Canellos* * http://iocanel.blogspot.com Apache Karaf http://karaf.apache.org/ Committer PMC Apache ServiceMix http://servicemix.apache.org/ Committer Apache Gora http://incubator.apache.org/gora/ Committer * -- *Ioannis Canellos* * http://iocanel.blogspot.com Apache Karaf http://karaf.apache.org/ Committer PMC Apache ServiceMix http://servicemix.apache.org/ Committer Apache Gora http://incubator.apache.org/gora/ Committer *
Re: Karaf-Cellar Install Error
A fix for this has been committed to trunk and merged to branch. Thanks for reporting it! -- *Ioannis Canellos* * http://iocanel.blogspot.com Apache Karaf http://karaf.apache.org/ Committer PMC Apache ServiceMix http://servicemix.apache.org/ Committer Apache Gora http://incubator.apache.org/gora/ Committer *
Re: Cellar And Hazelcast Questions
Hi Gareth, I created a sample project based on the code you pasted in your previous email and it works fine for me. The only modification I did was was to create the default constructor on the PredTester class, but this is something that I don't think thats directly related to the problem you encountered. As I mentioned in my previous post as long as you set the thread context class loader everything should work fine. Now regardin your question about fragments. I think that using fragments would also work, but they have the drawback that you have to install the prior to hazelcast or refresh the hazelcast bundle afterwards. -- *Ioannis Canellos* * http://iocanel.blogspot.com Apache Karaf http://karaf.apache.org/ Committer PMC Apache ServiceMix http://servicemix.apache.org/ Committer Apache Gora http://incubator.apache.org/gora/ Committer *
Re: Karaf cluster showing some error while starting
This is not an error, but a warning. I will have a look at it. Is everything else ok? On Friday, August 12, 2011, Gnanaguru S gnanaguru.sattanat...@wipro.com wrote: Hi, I was successful with the karaf-cellar through karaf 2.2.2 . but when i install something in my cluster, the other cluster shows some error. also it shows even that cluster is restarted . (Image below ) http://karaf.922171.n3.nabble.com/file/n3248353/karaf-error-log.jpg help out Regards Guru -- View this message in context: http://karaf.922171.n3.nabble.com/Karaf-cluster-showing-some-error-while-starting-tp3248353p3248353.html Sent from the Karaf - User mailing list archive at Nabble.com. -- *Ioannis Canellos* * http://iocanel.blogspot.com Apache Karaf http://karaf.apache.org/ Committer PMC Apache ServiceMix http://servicemix.apache.org/ Committer Apache Gora http://incubator.apache.org/gora/ Committer *
Re: How to open Karaf Cellar Webconsole
Hi , The cellar webconsole integrates with karafs webconsole. You need to install karats webconsole feature and then install the cellar console feature. Then open karats webconsole and you will be able to see the cellar tab. Please note that currently there are only a few things you can do using the cellar webconsole. On Thursday, August 11, 2011, Gnanaguru S gnanaguru.sattanat...@wipro.com wrote: Hi I was unable to find any documentation regarding karaf-cellar webconsole. Kindly help out how to open it. It will be much useful. Cheers Guru -- View this message in context: http://karaf.922171.n3.nabble.com/How-to-open-Karaf-Cellar-Webconsole-tp3245785p3245785.html Sent from the Karaf - User mailing list archive at Nabble.com. -- *Ioannis Canellos* * http://iocanel.blogspot.com Apache Karaf http://karaf.apache.org/ Committer PMC Apache ServiceMix http://servicemix.apache.org/ Committer Apache Gora http://incubator.apache.org/gora/ Committer *
Re: Cellar And Hazelcast Questions
Could you sent me a small sample? -- *Ioannis Canellos* * http://iocanel.blogspot.com Apache Karaf http://karaf.apache.org/ Committer PMC Apache ServiceMix http://servicemix.apache.org/ Committer *
Re: Cellar And Hazelcast Questions
Hi Gareth,
Hazelcast is using Thread.getCurrentThread().getContextClassLoader() in
order to read object it exchanges over the cluster.
You may have to to change the context class loader before you create the
Map.
For example:
ClassLoader originalClassLoader =
Thread.currentThread().getContextClassLoader();
try {
Thread.currentThread().setContextClassLoader(getClass().getClassLoader());
//Do stuff here.
} finally {
Thread.currentThread().setContextClassLoader(originalClassLoader);
}
I know its not the most elegant thing to do, but it will get things
working.
--
*Ioannis Canellos*
*
http://iocanel.blogspot.com
Apache Karaf http://karaf.apache.org/ Committer PMC
Apache ServiceMix http://servicemix.apache.org/ Committer
*
Re: Is there a way to find a filtered interface using Aries jndi ?
Hi Charles, You can use something like this: osgi:services/javax.transaction.TransactionManager/(tx=JTA-Spring) On Thu, Mar 31, 2011 at 12:50 PM, Charles Moulliard cmoulli...@gmail.comwrote: Hi, I have filtered an interface !-- Export SpringJTATxManager -- osgi:service ref=JtaTransactionManager interface=javax.transaction.TransactionManager service-properties entry key=tx value=JTA-Spring/ /service-properties /osgi:service and I would like to know if I can perform a lookup on the filtered resource ? jndi(TransactionManagerName=aries:services/javax.transaction.TransactionManager) Regards, Charles Moulliard Sr. Principal Solution Architect - FuseSource Apache Committer Blog : http://cmoulliard.blogspot.com Twitter : http://twitter.com/cmoulliard Linkedin : http://www.linkedin.com/in/charlesmoulliard Skype: cmoulliard -- *Ioannis Canellos* * http://iocanel.blogspot.com Apache Karaf http://karaf.apache.org/ Committer PMC Apache ServiceMix http://servicemix.apache.org/ Committer *
Re: Installing a war-file in a feature
Hi Michael, It is possible to install war as a feature. Here is an example feature that installs a war file. feature name=activemq-web-console version=5.4.2 bundlewar:mvn:org.apache.activemq/activemq-web-console/ 5.4.2/war?Webapp-Context=activemq-web-console/bundle * /feature * * * * Ioannis Canellos* * http://iocanel.blogspot.com Apache Karaf http://karaf.apache.org/ Committer PMC Apache ServiceMix http://servicemix.apache.org/ Committer *
Re: Startup problems: javax.naming.NoInitialContextException: Unable to determine caller'sBundleContext
Hi Bengt, Do you install/uninstall anything between the restarts? On Tue, Nov 30, 2010 at 10:56 AM, Bengt Rodehav be...@rodehav.com wrote: I use Karaf 2.1.2. On a clean startup (the data directory is empty) everything works OK. However, when I restart Karaf (without cleaning out the data directory) I consistently get the following exception: *Exception in thread JMX Connector Thread [service:jmx:rmi:///jndi/rmi://localhost:1099/karaf-root] java.lang.RuntimeException: Could not start JMX connector server* * at org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:103) * *Caused by: java.io.IOException: Cannot bind to URL [rmi://localhost:1099/karaf-root]: javax.naming.NoInitialContextException: Unable to determine caller's BundleContext* * at javax.management.remote.rmi.RMIConnectorServer.newIOException(RMIConnectorServer.java:804) * * at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:417) * * at org.apache.karaf.management.ConnectorServerFactory$1.run(ConnectorServerFactory.java:101) * *Caused by: javax.naming.NoInitialContextException: Unable to determine caller'sBundleContext* * at org.apache.aries.jndi.OSGiInitialContextFactoryBuilder.getInitialContext(OSGiInitialContextFactoryBuilder.java:53) * * at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)* * at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)* * at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:316) * * at javax.naming.InitialContext.bind(InitialContext.java:400)* * at javax.management.remote.rmi.RMIConnectorServer.bind(RMIConnectorServer.java:625) * * at javax.management.remote.rmi.RMIConnectorServer.start(RMIConnectorServer.java:412) * * ... 1 more* Does anyone have any idea what could be wrong? I'm thinking there may be timing errors. Note that the exception is only logged to the console - not to the log file. Perhaps it occurs before the logging bundle is installed. I haven't seen this in previous versions of Karaf (2.1.0 and 1.6.0) but I've also added and changed a lot of bundles in addition to upgrading to Karaf 2.1.2. Thus I don't know for sure if this is a problem specific to Karaf 2.1.2. /Bengt -- *Ioannis Canellos* http://iocanel.blogspot.com Integration Engineer @ Upstream S.A. http://www.upstreamsystems.com
