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

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

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

On Wed, Feb 3, 2010 at 8:30 AM, Blake Rodgers <bro...@ev...> wrote:
> Hello Leif,
>
>
>
> I apologize the duplication. I sent an earlier email with a screenshot, but
> it was bounced due to file size. I'll restate the problem more clearly.
>
>
>
> I am using a service we call vConnect on a Mac OS X 10.5, using the Jar
> wrapper integration method 4. The service is started by calling the wrapper
> script from an InstallAnywhere installer with the "start" argument at the
> end of the installation - the service starts up correctly.
>
>
>
> I visually check and see the process (wrapper) running in the Activity
> Monitor, and it has the same process ID as was in the wrapper's pid file.
>  When I try to stop the service manually from the Terminal, I get the
> following:
>
>
>
> ./run_app_script stop
>
> Stopping vConnect….
>
> Removed stale pid file: /applications/vconnect/bin/ ./vConnect.pid
>
> vConnect was not running.
>
>
>
> I checked the bug list, and a similar bug is listed as fixed, and others
> with similar problems.
>
>
>
> Interestingly, after the service is installed and started, if I then
> manually force quit /kill the process in the Activity Monitor, I can start
> and stop the service from the command line of a terminal by running
> ./run_app_script start , or ./run_app_script stop, even if I close the
> terminal I started it in and stop it in another one.
>
>
>
> I suspect that the stale pid issue has something to do with the service
> having been started by a call to the service script from within
> InstallAnywhere. Regardless, the service wrapper should be able to see that
> the pid file is not stale.
>
>
>
> Thanks,
>
> Blake Rogers
>
> Eveo