Re: [Wrapper-user] Re: Windows 2003 support and restart issue

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

Sam,
Can you post your wrapper.conf file.   I still can't think of anything 
that the Wrapper could
possibly be doing to cause this.  But I am curious about how the service 
is being configured
to run.   System user, or are you specifying a specific user to run as.
Also wondering about your wrapper.log file.  It is specified using the 
following property:
wrapper.logfile=../logs/wrapper.log

If the Wrapper is unable to write to that file for any reason, it will 
try writing to
./wrapper.log  Failing that, it will create a file in the 
Windows\system32 directory.

> >Strange. Where those two times on the same system? Or different ones? 
> It has occurred on two different systems, both running Windows 2003 
> and having varying amounts of windows updates completed.
>
> >I can't think of anything having to do with the Wrapper that would be 
> causing this.  Were there any
> >other files being accessed by that JVM? Did they also get deleted?  
> It does not appear that jvm related files are remove, only those files 
> related to the java service wrapper and listed in the wrapper.conf 
> file in the classpath.  In my case, this was our .jar files for both 
> services that had this issue occur, and the associated library files.
So you have seen this with multiple applications running? ...
> >Was the wrapper.log file still there?
> There is no wrapper.log file present (the wrapper.exe, .dll and .jar 
> are all removed - but the services do remain in the windows services 
> list) - where would the wrapper.log be located, and would it only be 
> created if particular log settings were in place in the wrapper.conf's?
See above.
> >Does it show that the JVM and Wrapper shutdown cleanly before the 
> reboot, or did the system >appear to shutdown suddenly?
> The system does not shutdown on its own, we merely performed a reboot 
> after an install and have now seen this occur 3 times (all the more 
> reason perhaps to move to our UNIX solution exclusively)
I have never seen or heard of any problems like this before, so that may 
still be
a bit hasty.
> I appreciate the quick response and the help though. Thanks Leif
No problem.  Still no help though :-/

Cheers,
Leif