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

[Leif M. <le...@ta...>]

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
>  
>