What are you putting in to be blacklisted? The reason you see it after a restart is because you initially didn't install it with cellar's bundle install command, so it only started on that node. When you shutdown and bring the nodes back up, that bundle ends up being synced because the blacklist/whitelist rules don't prevent it.
If yoh put bundle.jar in as the filter, it won't work. You need to see what the symbolic name is that it's being deployed as. You should see it tell you in the logs. What do you want to achieve with Cellar on those two nodes? And why is the bundle failing? There has to be something missing. Are you sure it started up when you only have one Karaf running? I don't see much to go off of. What is in the datasource.xml? I don't see this as a bug because if the bundle can't install correctly then the cluster will keep trying to sync it. It would help to know why it can't startup. Cellar isn't able to fix a bundle that won't start, the developer needs to fix the bundle. Otherwise do some research on deploying xml files on karaf so you understand how they work and then read the docs on how to blacklist the bundle. You have to understand how to reference a bundle before you can know what to blacklist. Ryan On Jul 10, 2014 6:22 PM, "asookazian2" <[email protected]> wrote: > this seems to be a bug but the workaround JB suggested to blacklist the > bundle for the datasource xml (use la -l to find the location and then > update bundle blacklist inbound/outbound in > etc/org.apache.karaf.cellar.groups.cfg) > > > > -- > View this message in context: > http://karaf.922171.n3.nabble.com/bundle-in-lifecycle-infinite-loop-tp4033960p4034146.html > Sent from the Karaf - User mailing list archive at Nabble.com. >
