> From: Yiannis Mavroukakis > Sent: 8. siječanj 2004 16:34 > > Would it not be possible to bind JNI under a single worker > and then isolate that worker from the rest of the pool > (possibly provide the ability for workers to carry some sort > of identification bit with regards to who can access them)?
That was the thing that I considered, but again if you have multiple workers, what would be the benefit of having that much Tomcat instances running. So either you have a single worker with the single TC instance launched or none. Having single worker running TC, keeping the rest 30 without would make the entire thing unusable, cause you cannot bind a client to the specific worker process. Even if you could there is no way that will assure you that the new request will get served by that particular jvm enabled worker. The JK2 code (from CVS) will in that case refuse to load the inprocess jvm, and the code snippet in you exhibit is meant to be used for that. At least the code was designed to do that (on more then one child process, kill the jvm channel). > I'll be more than happy to volunteer for the documentation, > just point at the right direction :) > Have no idea. If I would, I'd probably wrote something already. What do you think is the right place to start? MT. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
