On 13/07/2016 15:20, Jäkel, Guido wrote: > But if there is a certain request to some MBean while the App is > starting, there will be a request to the application (via > catalina-exec). And then, as a race condition, the initialization of > the Spring framework, esp. the bean wiring will fail with lots of > exceptions because this is not thread-safe. > > If this additional (failing) request is processed fast enough, the > application will be usable due to initialization via the normal > servlet lifecycle request. But if it's as a race condition in the > other way round, the application will be not usable afterwards.
I've been through the MBean descriptor for a web application and as far as I can tell, reading of all of the attributes is passive. It might return a few unexpected nulls or maybe thrown an exception but it shouldn't trigger any additional initialization. We need to find out what is triggering the second, unwanted initialization. You'll need to add some logging to your app to capture the relevant stack trace. When you have it, post it here. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
