Re: [Wrapper-user] Services dependency not preserved when system re-starting

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

Jindong,
    Unfortunately this is because of the way Microsoft implemented the 
ServiceManager.
The ServiceManager ignores the dependencies on shutdown and requests 
that all
services are stopped at the same time.  Depending on how quick each one 
responds,
you will see the random behavior that you have observed.

    I would love to be able to fix this for you.  But I believe it is 
out of my hands and
just something that Windows users will have to live with.  If anyone has 
any ideas...

Cheers,
Leif

Jindong Li wrote:

> Hi there,
>
> I have exposed the rmi registry and my application as windows services 
> using the wrapper, all worked very well, there's just this one thing 
> we noticed just recently, since my application depend on the rmi 
> registry to be up, so I defined my app dependent on the rmi registry 
> service.
>
> If I manually stop rmi registry service, the service manager knows 
> that my app service is dependent on the rmi registry service and ask 
> me to confirm that my app service will be stopped as well...all is 
> fine - my app service stopped first then the rmi registry service.
>
> However, when re-starting the machine with those 2 services already 
> running and set to Automatic mode, it seems to me that the Shut-Down 
> events are sent to those 2 JVM's in a random fashion - sometimes the 
> rmi registry services was shut down before my app service causing my 
> app not shutting down cleanly and logging err msgs.
>
> What's the reason for this?
>
> I'm using 3.0.3.
>
> Thanks and any input would be greatly appreciated.
>
> Jindong.
>