Re: [Wrapper-user] RE: questions

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

The Wrapper controlls the single JVM that it directly launches.  That JVM is
protected from the Windows OS killing it when a user logs off because it
loads the Wrapper.DLL.  That DLL intercepts the logoff control signal.

The 3 JVMs that you are spawning will not be protected so they are still
receiving the logoff control signals and exiting.

Is there any reason why you can not wrap those 3 JVMs in Wrappers as
well?  Either set them up as NT services themselves or spawn their
Wrappers in console mode as you are currently doing with the JVMs now.

If you are worried about launching your JVMs in a particular order, you can
specify server dependencies in the wrapper.conf file.  That will make the
NT service manager start and stop the services in the correct order.

Cheers,
Leif

Jindong Li wrote:

> One more thing I noticed, if I log off the system with the service 
> running, those 3 JVM's that started by my java application which is 
> wrapped by the service wrapper are killed, reason I know this is 
> happening is that, one JVM is used to start TOMCAT, once I logged off, 
> I was not able to talk to the WebServer on port 8080 anymore.
>
> If I then log on again, the service status is still showing running 
> but really it is just the wrapper that's running, all JVM's started by 
> the service seem to be no longer running...
>
> Is this because how the windows log off process works?
>
> Anybody else tried log off, if so after logging off, is the 
> application still running as expected?
>
> Thanks,
>
> Jindong.
>