Hi, For me, it seems a race condition while starting your services, as your services are required.
For instance, the DOMEntityOwnershipService and BindingNormalizedNodeSerializer services are not starting, blocking the eos-binding-adapter and so so. So it's causing a cascading. It's maybe related to your config-manager that seems to be stuck. Maybe the config-manager is a ManagedService providing the services and as it's stuck, the services are not registered. A possible quick workaround is to set the service as optional in the blueprint container. However, I would take a look in config-manager. Regards JB On 18/02/2019 08:55, Vikram Darsi wrote: > Hi Team > > Have a small question on blueprint container startup: > Very few times, blueprint containers of our application fail to come up by > throwing TimeoutExceptions > and if we restart the application, things are getting resolved. > > karaf.log <http://karaf.922171.n3.nabble.com/file/t497773/karaf.log> > > Karaf log file is attached. > > Not sure How to reproduce this issue, but is happening intermittently, if it > appears, How can I debug it further and what can be tweaked to fix such > issues? > > > > -- > Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html > -- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
