[Wrapper-user] service wrapper 3.3.9 - WrapperJarApp - "stop" doesn't shut down service, incorrectly returns stale pid file

[Blake R. <bro...@ev...>]

Hey Leif,
Thanks for getting back to me so promptly. 

I modified the Tanuki wrapper script - some stuff removed about binaries, and the block where the pid is checked commented out. so it stops the process referenced in the wrapper pid file without checking whether or not it's the "correct" process - since it was determining that it was NOT the correct process - maybe due to the service being started up with commands from the InstallAnywhere installation process. I'm attaching the wrapper script.

Regarding the screenshot attachment, the wrapper process in the activity monitor was inadvertantly hidden because the window scrolled when I took the screenshot for some reason. I took another but then I didn't send it because it was too large in size. Okay, so.. 

InstallAnywhere calls a script which directly calls the wrapper's shell script with argument start. In accordance with the instructions on 

http://wrapper.tanukisoftware.org/doc/english/integrate-jar-nix.html#allTogether

Even though the wrapper in the running process is the current one, the script was determining it to be stale. I visually check and see the process (wrapper) running in the Activity Monitor every time I test, and it has the same process ID as was in the wrapper's pid file. For instance, this is not a case of two Wrapper processes running simultaneously.

Blake



Blake,
I saw the earlier message with the screen shot as well.   In the
process list, I saw the Java process, but not the Wrapper process.
Before I look into this too far, could you please confirm how
InstallAnywhere is launching your application?   Is it launching the
Wrapper's shell script (run_app_script) or is it launching the Wrapper
or Java directly?

The Wrapper's shell script is looking for a PID file which it expects
contains the PID of a running Wrapper process.   Any other processes
will be assumed to be stale.  This is done to avoid accidentally
shutting down something other than a Wrapper process.  On some UNIX
platforms, PID files have been known to survive system restarts after
OS level crashes.

Cheers,
Leif
***************************