|
From: Ralph S. <ral...@we...> - 2005-06-07 14:32:43
|
Hi Leif, even when the 100 JVMs are launched as child processes from a single JVM via Runtime.exec, I encounter no problems. Could it be that the pings of the JVM by the wrappers are problematic when starting more and more wrappers? Just a guess ... Cheers Ralph wra...@li... schrieb am 07.06.05 15:06:06: > > 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 > > > > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput > a projector? How fast can you ride your desk chair down the office luge track? > If you want to score the big prize, get to know the little guy. > Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20 > _______________________________________________ > Wrapper-user mailing list > Wra...@li... > https://lists.sourceforge.net/lists/listinfo/wrapper-user ______________________________________________________________ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193 |