On 15/06/2012 01:05, Oguz Kologlu wrote: > > On 15/06/2012, at 4:35 AM, Christopher Schultz wrote: > > Oguz, > > On 6/14/12 6:24 AM, Oguz Kologlu wrote: >>>> I've seen this question bounce around some threads but there's >>>> really no good answer. >>>> >>>> I'd like to use the Tomcat 7 thread pool as worker threads for >>>> Quartz Scheduler. > > Why would you want to dip-into the request-processor pool instead of > maintaining a separate one? > >> To conserve shared resources between web apps.
Why? What shared resource? That's not a thread pool - it's a resource pool. >> Similarly Tomcat has a built in DB connection pool / the DBCP is often a >> shared resource. If you're really describing a shared pool of resources (that are not plain threads), then use commons-pool & hook it up to whatever resource it is you're really trying to manage. p >> Hmm. I think perhaps I can configure a common thread pool and expose it via >> JNDI to the web apps. > >> http://tomcat.apache.org/tomcat-7.0-doc/jndi-resources-howto.html#Generic_JavaBean_Resources > > >> Oz > > > >>>> Is there a way to access the thread pool from a web app? > > You can't. > >>>> Any other suggestions? > > Use your own thread pool. > > -chris >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> >> > > -- [key:62590808]
signature.asc
Description: OpenPGP digital signature
