On 15/06/2012, at 4:35 AM, Christopher Schultz wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > 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. Similarly Tomcat has a built in DB connection pool / the DBCP is often a shared resource. 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 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.17 (Darwin) > Comment: GPGTools - http://gpgtools.org > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAk/aLw4ACgkQ9CaO5/Lv0PBdNwCgv2p3RjU/Kpp3EYk1CB57MIdy > 1EAAnRwis/kCbRrpNb5e9swweSiJ/2WX > =Ytn6 > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > >
