I am attempting to run a background Java/JRE listener process. After 15-30 seconds it gets killed.
Does DH have some kind of watchdog daemon that kills bg processes?
The start/stop/status script nohup’s and &'s the process. Environment variables have been exported in the parent. The main bg process has 11 java threads to it. Is there a limit on the number of background processes you may have?
I thought you might have to run bg process from your main server account, but in 24 hours the main server ftp hasn’t been converted to shell yet.
By default there are 8 points of nice added so that shouldn’t be the problem. I ran the script foreground/debug and watched the processes with TOP, and they aren’t taking any resources at all.
This is, alas, a chat system with a Java listener on the server and a client applet. Sales told me that as long as it wasn’t IRC I could give it a shot as long as system resources weren’t hogged. Could there be restrictions on the ports that can be used? Can ports be used at all?
There are two CRON jobs associated with the system as well. One that restarts the main processes at 4:00 a.m. (JAVA memory-leak precaution) and a watchdog that checks every 15 minutes to make sure it’s still up, and restart if not. Could these be the problem?
Support must understandably be busy with the datacenter move tonight as I haven’t received a response from the trouble ticket either.
Sorry to ask so many questions in one email, but the software is $500 and I want to make sure it works right before I plunk down more than double what the site cost. Any feedback from you old-timers out there would be very much appreciated.