@Gert, When the deploy fails, servicemix still works and other bundles get deployed, but the deployment of feature/bundle in question is random. Sometimes it deploys, sometimes not.
In regards to the logging, currently our logging level is at INFO. When we turned it to DEBUG or TRACE we did notice that servicemix would hang up. So unfortunately, even with it at INFO, we still notice the issue. Thanks for the response! Justin On Wed, Feb 8, 2012 at 2:30 AM, Gert Vanthienen <[email protected]>wrote: > L.S., > > What exactly happens when the deploy fails? Just nothing happening at all > or do you see the container get deadlocked as well? > > I suspect you might be impacted by > http://team.ops4j.org/browse/PAXLOGGING-99 and > http://team.ops4j.org/browse/PAXLOGGING-124 - if that's the case, you can > probably get around it by reverting the log level to INFO when starting the > container. > > Regards, > > Gert Vanthienen > ------------------------ > FuseSource > Web: http://fusesource.com > Blog: http://gertvanthienen.blogspot.com/ > > > On Wed, Feb 8, 2012 at 2:05 AM, Justin Beltran <[email protected]> wrote: > > > All, > > > > I'm encountering a weird issue with ServiceMix 4.4.1 where ServiceMix > will > > sometimes install a feature and bundle, but then on restart it does not > > deploy successfully. After a couple of restarts, it'll deploy. It's > very > > random when it actually does work. > > > > If I turn info logging on I see the corresponding messages: > > > > org.apache.karaf.features.core - 2.2.2.fuse-00-06 | Installing feature > > <<feature name>> > > org.apache.karaf.features.core - 2.2.2.fuse-00-06 | Installing bundle > > <<bundle name>> > > > > But nothing actually happens. When it does work I see the corresponding > > logging tied to that feature and bundle. > > > > Any ideas or is there any other information I could provide to pinpoint > > what's going? > > > > Thanks! > > Justin > > > > > > > > >
