On Sun, 9 Dec 2001, Scott M Stark wrote: > This can't be done in general because of the loosely coupled nature > of the architecture. You can plug-in any off the self servlet container, > or in general, any component that has its own thread pool management.
True, as the Jetty stuff does, which Anatoly noted. But what about the core JBoss components? It might be nice to have a centralized controller of the threads in use by the core system. > Also, even if there is a centralized thread pool, this does not prevent > a Runnable from spinning. You may be able to centralize an interrupt > call dispatch, but that does not prevent the Runnable from catching it > and resuming its spinning ways. Ya, I more thinking for thread creation and pooling... if a runnable is gonna go nutz, well its gonna go nutz either way. --jason > > There was some talk a long time ago about using a centralized threading > > system. Is this still on the burner somewhere? Could we create a > > ThreadController MBean, that would have a single thread pool (or > > configurable set of pools), then each component that needs to thread, > would > > use it to access its threads? > > > > The point being to have one component which is responsible for 95% of the > > threading in the server (there will probably be a small percent which > can't > > be controlled by it due to bootstrap or conditions). > > > > It probably needs some more time to bake, but I think it might help > improve > > threading using inside JBoss. _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
