f.apache.org>
Subject: Re: More entropy on bundle startup.
Try the load-test command inside the karaf console. It randomly starts / stop
/ refresh bundles with multiple threads in loop, so such things are quickly
seen usually.
2016-07-13 22:56 GMT+02:00 Benson Margulies
<ben...@basistech.
Try the load-test command inside the karaf console. It randomly starts /
stop / refresh bundles with multiple threads in loop, so such things are
quickly seen usually.
2016-07-13 22:56 GMT+02:00 Benson Margulies :
> Folks,
>
> We've had a couple of incidents of latent
We use DS for most of our services, but we have a few down at the
activator level.
I appreciate that the fixes to the bugs involve service tracking. The
problem is _finding_ the bugs.
Yes we use featuresBoot.
featuresBootAsynchronous=false
On Thu, Jul 14, 2016 at 9:56 AM, James Carman
You are using featuresBoot? Do you have featuresBootAsynchronous=false in
your org.apache.karaf.features.cfg file?
On Thu, Jul 14, 2016 at 9:33 AM Benson Margulies
wrote:
> I don't think so, no. I do not do any dynamic installation. I use the
> Maven plugin to make an
What kind of services do you create? Blueprint, Component, direct
Activator?
I use Component, and the Component waits for the required components to
be available and then starts.
I have had issues in the past with badly coded direct Activators not
starting in the correct order. I then
I don't think so, no. I do not do any dynamic installation. I use the
Maven plugin to make an assembly with all the features I need. I then
observe that the startup order is not deterministic from machine to
machine, and it is particularly prone to change when I stop and start
the container
Hi Benson,
I guess you are using the deploy folder, so the fileinstall deployer,
right ?
Regards
JB
On 07/13/2016 10:56 PM, Benson Margulies wrote:
Folks,
We've had a couple of incidents of latent problems stemming from
invalid assumptions on bundle start order. Everything seems to be
I love this idea! We’ve been fighting the same issues as well.
-Nick
On 7/13/16, 4:56 PM, "Benson Margulies" wrote:
>Folks,
>
>We've had a couple of incidents of latent problems stemming from
>invalid assumptions on bundle start order. Everything seems to be
>fine, then
Folks,
We've had a couple of incidents of latent problems stemming from
invalid assumptions on bundle start order. Everything seems to be
fine, then some trivial change reveals that we've failed to ensure
that service 'a' is available before component 'b' needs it. by and
large, we use DS to get