Hello,
Yes I did and tried again now. I waited for all the bundles to be marked as Active and blueprint marked as Created, and then I still waited for some time before starting the node 2. It is still marked as in Failure on node 2. Could the configuration mentioned in the first post be wrong? Because this only happens when the nodes see each other. If I disconnect the second node from the network, both of the nodes start just fine (only then the problem is that when I reconnect it, it takes about 5 minutes to get discovered by the other node and for it to discover the other node). Could the Hazelcast cause this? Is Hazelcast configuration possibly wrong? I would like to avoid having to disconnect the node every time I need to restart the karaf. Regards, DD -- View this message in context: http://karaf.922171.n3.nabble.com/Cellar-bundle-blueprint-faliure-tp4025940p4025943.html Sent from the Karaf - User mailing list archive at Nabble.com.
