Re: [Wrapper-user] Net stop reports service could not be stopped

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

Eric,
    What exactly are you seeing in the command window when you run "net 
stop myapp"?

    Looking at the wrapper.log file, everything appears to be 
functioning correctly.  The
Wrapper is exiting with an exit code of zero and it appears to be doing 
so in a timely
manner. 17 seconds.

    I did notice that your application appears to be calling System.exit 
at some point
during the shutdown process.  The stop main method is returning, but the 
shutdown
hooks are being started.   To avoid deadlocks, the wrapper goes into a 
mode where
it only waits 5 seconds for your threads to complete.  After 5 seconds, 
you still have
15 non-daemon threads running so your application has not shutdown 
completely
at that point.  The workaround is needed because at least one of those 
15 threads
is frozen within a call to System.exit and will never complete.  With 
Java 5, I may
may be able to figure out which threads are in System.exit and make this 
work a
little better.

    I don't believe that would be causing any errors from net stop however.

Cheers,
Leif

Eri...@Bu... wrote:
>
> Leif,
> The service takes a little while to stop, it's an application server 
> but I don't think a timeout should be occuring based on the wrapper 
> debug output and information that I'm reading about the service 
> control manager.  I have tested the wrapper -t and -p functionality 
> and it works as you state, but I'm dealing with a user that wants to 
> do everything the standard MS way and also may be using the service 
> window.  I'm attaching the log file, where I just do a net start 
> followed by a net stop and it doesn't seem long enough to be causing 
> an error return from net stop.  Have you looked at sending 
> STOP_PENDING status messages to help with this issue, just something I 
> saw in the Handler documentation?  
>
> Eric