Hello Rob, Rob Y wrote: > ... At very least, it'd want to start up a > JVM with a different classpath ...
If it's just the distinct classpath you are worried about, you are not forced to use separate JVMs. You can use plain JNI to: define classes, create custom class-loaders, attach threads, etc. This would allow you to get your code executing on an already existing JVM regardless of its 'java.lang.classpath' system property. However, other JVM options like "-Xmx..." etc may present hard barriers to sharing a JVM. > My app's structured Apache-like as a transaction processing system with a > pool of shared processes as opposed to a single multi-threaded process... > ... I think it'd be better to just exit my > process after creating the XLS and let the system dispatcher launch a new > copy as needed... Have you considered having just one dedicated JVM process that is shared by all the other app processes, and stays up permanently? The downside is that you'd have to figure out the inter-process communication, but you'd get to avoid the logic to decide when to kill processes in order to create new JVMs. > Does anybody know how Apache Tomcat deals with this? Presumably it's got a > pool of processes that need to run different Java code on different > invocations. I have only ever seen Tomcat running as a single process. Tomcat web-apps get distinct class-paths through separate class loaders. I guess many instances of Tomcat can be configured to run together on the same machine, but I don't think Tomcat has anything like Apache HTTP Server's MPM. regards, Josh --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
