Hi, I'm no expert on this.
I'm just wondering what's the "risky" part. Is database pooling any different than this idea, in that you are still dependent on something outside of Java mis-behaving and is platform-specific. And would there be anything "non-portable" except for the JNI part, which of course is platform-dependent. Cheers, Oscar On Wed, 2 Jul 2003, Shapira, Yoav wrote: > > Howdy, > You can use commons-pool for this. > > The approach itself (pooling processes) is risky and likely to be > non-portable. > > Yoav Shapira > Millennium ChemInformatics > > > >-----Original Message----- > >From: James Carpenter [mailto:[EMAIL PROTECTED] > >Sent: Wednesday, July 02, 2003 4:38 PM > >To: tomcat users list > >Subject: Java Process Pool > > > >Does anyone know of a convenient way to create a Java process pool. A > >thread pool won't work as I am trying to pool some JNI code wrapping a > C > >library that isn't thread safe. > > > >I would rather not have to create my own pooling mechanism. > > > >Sincerely, > >James Carpenter > >Email: [EMAIL PROTECTED] > > > > This e-mail, including any attachments, is a confidential business communication, > and may contain information that is confidential, proprietary and/or privileged. > This e-mail is intended only for the individual(s) to whom it is addressed, and may > not be saved, copied, printed, disclosed or used by anyone else. If you are not > the(an) intended recipient, please immediately delete this e-mail from your computer > system and notify the sender. Thank you. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
