Are you using Felix or Equinox?

Using Felix, we've seen bundle corruption issues (see
http://karaf.922171.n3.nabble.com/bundle-corruption-with-felix-and-karaf-3-0-2-td4037669.html)
that sound similar to what you describe when Karaf isn't shut down
properly.  I think if you use Equinox, the behavior may be better (or at
least different), but you can also disable pre-emptive shutdown which has
helped for our configuration quite a bit.

On Wed, Apr 22, 2015 at 6:38 AM, mbelling <[email protected]> wrote:

> I tried searching for this issue, but I wasn't able to find something like
> it
> with the searches I tried.
>
> Occasionally a co-worker of mine has an interesting issue where they will
> have a running machine with Karaf, and need to do a reboot on the machine
> for some unrelated reason.  Upon the machine coming back up, most of the
> bundles that were running before, are no longer running, and are no longer
> listed on the web console.
>
> I checked the data directory and the bundles are still in the cache, but at
> this point I don't know where to begin diagnosing what is going on.  Is
> there logging I can turn up, or commands I can run to try to figure out why
> the bundles did not start on a reboot?  Can anything in the cache directory
> files help me out?
>
> If it helps, the bundles are installed via a feature install.  We are using
> hibernate, and I have this suspicion that it might be the culprit, but like
> I said before, I don't know what to look at to confirm it.  All I know is
> that 'some' of the hibernate bundles come back up after the reboot, but
> some
> do not.  And if hibernate is not able to start, I assume that chains to the
> rest of the application that depends on it.
>
> There is nothing in the log after the reboot to indicate anything is wrong.
>
> Any information is welcome,
> ~Matt
>
>
>
> --
> View this message in context:
> http://karaf.922171.n3.nabble.com/Bundles-no-longer-listed-or-started-after-machine-reboot-tp4039882.html
> Sent from the Karaf - User mailing list archive at Nabble.com.
>

Reply via email to