About cluster:node-ping command in Cellar

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

Re: About cluster:node-ping command in Cellar

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

Re: assembly : bundle + dependencies?

Hi Andrei, I'm stuck with a customer this morning, I will get back to you asap. Regards JB On 02/09/2012 04:50 AM, Andrei Pozolotin wrote: Jean-Baptiste: 1) thank you for a great post: http://blog.nanthrax.net/2011/12/do-you-know-the-apache-karaf-maven-plugins/ 2) in your

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

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

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

Re: Console of child instance didn't react same as root.

I don't have a windows environment on hand to test the shell, however looking deeper into the issue it appears some work was done for 3.0.0-snapshot to specifically handle windows terminals (https://issues.apache.org/jira/browse/KARAF-1071 - part of

Re: karaf test framework: multiple test classes files in the same karaf instance

Hey Giacomo, Well, paxexam-karaf completely relays on pax exams features in this context. Since there is no such feature in pax exam right now (at least I don't know a workaround) it's also not possible in paxexam-karaf. BUT maybe Toni or Harald know some internal workaround/hack to make this

RE: About cluster:node-ping command in Cellar

Hi, JB, The Cellar version is 2.2.3. features:addurl mvn:org.apache.karaf.cellar/apache-karaf-cellar/2.2.3/xml/features features:install cellar I've made nothing change to the cellar configuration files in the etc/, keep the default value in the etc/ org.apache.karaf.cellar.instance.cfg :

Re: About cluster:node-ping command in Cellar

Hi Xilai, after checking in the code, in 2.2.3, the timeout handling is not fully fixed. So I think that you raise the timeout. I advice you: - to check if you don't have Windows firewall/firewall blocking the multicast/hazelcast messages - to switch in static host definition in the