You need to make sure that you use nohup when you start it
the following will work:
nohup ./server.sh &
When you logout of ssh/close your terminal the application receives SIGHUP signal, this will kill the server unless you use nohup.
Also if you are wanting to run the server as a daemon, the newer version of messenger in CVS has an init script. The script is in the bin/extra directory. Make sure you follow the instructions in the script.
./server.sh & starts the program in the background which allows me to logout and have the server keep running. I logout to test it and the server still runs.
I will start it with Nohup to see how that works, I am just curious as to why it is necessary.
Try the nohup. The server shouldn’'t be running if you run it in the background and just logout.
As I mentioned earlier when you close your ssh connection the SIGHUP is sent to all your child processes. Background processes will also receive the hangup signal.
The java virtual machine will shutdown if it receives this signal. The nohup command will ignore the signal and make sure that its child processes do not receive the server.
If nohup fails, is there a chance that there is something else running that would be sending a SIGKILL signal to the application? It looks as if the server is stopping nicely, meaning it is receiving SIGHUP or SIGKILL and not crashing or receiving SIGTERM.