RE: [Wrapper-user] wrapper not shutting down on Solaris

[Pritchard, S. <SP1...@te...>]

I've fixed the problem.  I had changed the location of the pid file in 
the .conf file but not in the script that starts and stops the program.
Once I synched the
two, everything was fine.

I suggest that a comment be added to the conf file warning users that the
PID file path and name must match that in the startup script.  

I've been quite happy with wrapper.  Thanks for the good product!

Sean

-----Original Message-----
From: Pritchard, Sean 
Sent: Thursday, January 09, 2003 2:15 PM
To: Wrapper User mailing list (E-mail)
Subject: [Wrapper-user] wrapper not shutting down on Solaris


Hi,

	I downloaded the wrapper source and build it on Solaris 9.  I got my
app up and running with no significant trouble.  But when I went to stop my
app, I got a message that my app was not running.  I know this wasn't true
because I could see the process after issueing a "ps" command and because my
app's log files were continuing to show new messages as the app ran.

	The one change I mad to the conf file that seemed significant to
this problem is I set "wrapper.pidfile=./multiplexer.pid"  I did this
because I did not have write permissions to the directory that is set by
default.  I can see the .pid file being created and it contains the correct
process ID.  When I manually stop the app with the kill command, the .pid
file is deleted.  So I conclude from this that wrapper is finding the file
without problem.  I use a script based on testwrapper to start and stop the
app.  I only changes the app name, app long name, and conf file location,
and the shebang to reflect my location of sh.

	I turned on debug logging and watched the JVM log a series of pings
and responses.  So it seems wrapper was successfully monitoring the VM.
These pings continued after I attempted to stop the app.  A snippet of the
console output is show below.  My in-line comments start with "//"  I
inserted whitespace for readability.

	Can anyone suggest what I should do to continue troubleshooting
this?  I'm at a loss.  BTW, I successfully built on RedHat linux and did not
encounter this problem.

Thanks in advance,
Sean


jvm 1    | Send a packet 103 : ok

//now I try to stop the app (using my script that is based on testwrapper)

bash-2.05$ ./multiplexer.sh stop
Stopping Teradata CRM Email Multiplexer...
Teradata CRM Email Multiplexer was not running.

//my app did not stop, pings continue

bash-2.05$ jvm 1    | Received a packet 103 : ping
jvm 1    | Send a packet 103 : ok

// I check ps to confirm the app is still running

bash-2.05$ ps -eaf | grep multiplexer
sp180007 29584 26899  0 13:54:07 pts/5    0:00 grep multiplexer
sp180007 29562     1  0 13:53:28 pts/5    0:00 ./wrapper
../config/multiplexer.conf
bash-2.05$ jvm 1    | Received a packet 103 : ping
jvm 1    | Send a packet 103 : ok

//it is still running and pinging 



-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Wrapper-user mailing list
Wra...@li...
https://lists.sourceforge.net/lists/listinfo/wrapper-user