|
From: Leif M. <le...@ta...> - 2005-06-07 13:05:03
|
Ralph, were those 100 JVMs each launched from their own console or were they all launched as child processes of a single JVM like you are trying to do with your real applications? I have never tried exactly what you are trying. It sounds like a resource issue of some kind. A single JVM uses quite a few file handles. I am wondering if the parent Wrapper process is simply running out? I can't think of anything about the Wrapper itself which would be causing this directly... Leif Ralph Schreyer wrote: >Hello Leif, > >thank you very much for your answer. I turned on wrapper.debug=true and generated the output shown below, i.e. the JVM exits with code 6 (SIGABRT, afaik) > >In a test run, I started more than a hundred JVMs (each starting my Java service) on my PC without any problems. As soon as I wrap the calls into the Java Service Wrapper, the JVMs crash when starting more than ~ 30. > > >Cheers > >Ralph > > |