Re: [Wrapper-user] What are reasons a service wouldn't be able to start?

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

Jennifer,
    I am not aware of any such limit other than simply running out of 
system resources.
I have never tried running more than a few instances at a time.  
Certainly never that
many.  It took a while, but I tried running 30 instances as services 
today.  They all
started up promptly without any problem.   They were all light weight test
applications which only used about 3MB each however.

    When your #24 service fails to start.  What are you getting in your 
wrapper.log?
Please try it with wrapper.debug set to true.   The message that you are 
getting
comes from the service manager if the service takes too long to start.  
The Wrapper
is designed to send signals to the ServiceManager in a timely fashion to 
prevent this
message from ever showing up.  What does your memory and CPU usage look like
when you are seeing this problem?

Cheers,
Leif

Jennifer Kolar wrote:

> In trying to start multiple instances of my application, and thus 
> multiple services I seem to hit a limit where no matter how long I 
> give for a startup timeout, I always get the response
>
>     Unable to start the serivce- The service did not respond to the 
> start or control request in a timely fashion.
>
> Any ideas?
> I seem to hit this at what would be service # 24 or 25.  I can start 
> more services via copying registry keys around directly.. I just can't 
> start them w/ the wrapper.exe ..
>
> thanks
> Jennifer