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

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

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