Nope, no special activation. In this case, no activation at all actually. I'll see what happens after 4.2.2 comes out and if the behavior still exists I'll get you a thread dump.
Scott -----Original Message----- From: Jean-Baptiste Onofré <[email protected]> Sent: Wednesday, December 05, 2018 10:54 PM To: [email protected] Subject: Re: Related to the startup performance discussion Hi, Can you take a thread dump at startup and send to me ? Do you have something special in the activator/activate of your bundle ? Without some details, it's hard to say. Thanks, Regards JB On 06/12/2018 00:08, Leschke, Scott wrote: > FWIW, I also have something I see. I have a bundle that sits in the > Waiting state for a long time. A bundle:diag tells me it's waiting on > a particular service but, the service it's talking about comes from a > bundle that is Active, and the service itself has no dependencies and > has */immediate = true/* set. > > > > I also see this same thing but the service in question is the > org.osgi.service.jndi.JNDIContextManager that it doesn't resolve > against. Again, the bundles waiting on this eventually resolve but it > frequently takes a long while, like a minute or more. > > > > This happens under Windows Server 2016. > > > -- Jean-Baptiste Onofré [email protected] http://blog.nanthrax.net Talend - http://www.talend.com
