RE: [Wrapper-user] Limit on started JVMs under NT Service

[Christian C. <car...@ap...>]

Hi Leif,

My problem seems effectively related to resource limitation.
But my PC has 1GB RAM, and the behavior is the same on a 2GB RAM host. I
also tried to reduce the JVM max memory amount, by setting the
wrapper.java.maxmemory parameter, but nothing changed.

With all JVM running, my system memory usage is around 830 MB (which is
relatively high). I tried running the processes in console, and this works
fine. So the problem really deals with the NT Service execution.

When the system refuses to start the 17th JVM, I get no error. The JVM
stdout/stderr are redirected to files. These files are empty. I had a look
in the system event loggger, and I get an error like "Service did not
respond to start command within time". I guess this error is raised because
the Wrapper detected a JVM have been killed before (as the time out
mentionned value is 30s, and the JVM are killed immediately after being
started), and did not acknowledge its startup within time.

I'm now having a look on the Apache launcher, as I noticed Tomcat process
(also started as a child of one of my NT Services, built with Java Service
Wrapper) appears to be detached from the Wrapper process.

Cheers
Christian

> -----Message d'origine-----
> De : wra...@li...
> [mailto:wra...@li...]De la part de Leif
> Mortenson
> Envoyé : mercredi 1 mars 2006 19:09
> À : wra...@li...
> Objet : Re: [Wrapper-user] Limit on started JVMs under NT Service
>
>
> Christian,
> Another user had been running into a similar problem last year.
> The Wrapper does not contain anything which should be limiting the number
> of JVMs.  I have run tests with 32 JVMs, each running under their own
> Wrapper
> without any problems on an XP Home edition system.  I have not
> tried it with
> child process as you are doing however.
>
> Are you sure it is not a resource related problem?  What is your system
> memory
> usage?
>
> Have you tried running all of these applications in console mode rather
> than as
> services?
>
> When the system refuses to start a 17th JVM, what is the exact
> error you are
> getting.
>
> Are you able to start a 17th JVM from a console?  How about without the
> wrapper?
>
> Cheers,
> Leif
>
> Christian Cardinale wrote:
> > Hi everyone,
> >
> > I tried to install several NT services using the Java Service Wrapper.
> > Each of these services executes a JAVA program, spanning a couple of
> > JVMs (using basically the exec method from Runtime class).
> >
> > Let say:
> > Service NT_SVC1 : A java application, starting 8 children JVMs
> > Service NT_SVC2 : A java application, starting 5 children JVMs
> > Service NT_SVC3 : A java application, starting 5 children JVMs
> >
> >
> > The problem I encounter is that the system refuses to start more than
> > 16 JVMs. The 17th is killed as soon as it has been started
> > No matter the Wrapper started first, I'm always getting 16 JVM started.
> >
> > In my example : starting NT_SVC1, then NT_SVC2, then NT_SVC3, only 3
> > JVMs from NT_SVC3 are started.
> > If I kill 1 JVM from NT_SVC1 and I restart NT_SVC3, I notice 1 more
> > JVM is started from NT_SVC3.
> >
> > Is there any limitation in Java Service Wrapper, or in NT services
> > that I reached ?
> >
> > Any help would be appreciated.
> >
> > Best regards,
> > Christian Cardinale
> >
> >
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking
> scripting language
> that extends applications into web and mobile media. Attend the
> live webcast
> and join the prime developer group breaking into this new coding
> territory!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
> _______________________________________________
> Wrapper-user mailing list
> Wra...@li...
> https://lists.sourceforge.net/lists/listinfo/wrapper-user
>