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 <[email protected]>: > 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 this right, but there are a few cases where it > does not serve. > > I am wondering: is there some way to get _more_ randomness out of the > startup process, to shake out mistakes like this? > > thanks, > benson > -- ------------------------ Guillaume Nodet ------------------------ Red Hat, Open Source Integration Email: [email protected] Web: http://fusesource.com Blog: http://gnodet.blogspot.com/
