jboss stops running after a few hours on linux

davem Jul 27, 2003 10:43 PM

Hi,

I'm running Jboss 3.2.1 and Tomcat 4.1.24 on linux. After a few hours, jboss stops running. I think the problem has to do with the fact that jboss needs to run as a background process. I've run Jboss as ./run.sh -c projectname& to make it run in the background and I've also edited my run.sh file to make it run in the background.

I don't have this problem with Jboss 2.4 and I edited my run.sh file in the same manner.

One thing that is very curious is that if I run Jboss like
./run.sh -c projectname&, once jboss has started, it says the background process has completed. I think this is because the run.sh script has completed.

When I run Jboss using my run.sh script and in the file I use the "&" to send the process to the background, Jboss just stops running after a few hours. Typing in "jobs" reveals no background jobs.

The last part of my run.sh file looks like this:

# Execute the JVM
$JAVA $JAVA_OPTS \
-classpath "$JBOSS_CLASSPATH" \
org.jboss.Main "$@" &

Any help would be GREATLY appreciated.

Thanks in advance,

Dave

1. Re: jboss stops running after a few hours on linux

vashistvishal Jul 28, 2003 3:52 AM (in response to davem)

I didnt have any problems with jboss 3.2.1, I am using linux redhat8.0.
Have a look at thishttp://www.tusc.com.au/news_events/news_details.php?id=34
Hopefully this helps.
Actions
2. Re: jboss stops running after a few hours on linux

davem Jul 28, 2003 12:58 PM (in response to davem)

I checked that out and it doesn't really give me any info about why jboss might stop running...thanks though.

I'm still having this problem so if anyone else can help that would be great.
Actions
3. Re: jboss stops running after a few hours on linux

jonlee Jul 28, 2003 7:19 PM (in response to davem)

Is it related to your terminal session? That is; is it because your terminal session ends?

If not, does it terminate cleanly with server.log showing the shutdown sequence? Or does it just drop?

If it is not terminal session related, you can try one or combinations of the following:
1) increase the heap memory (-Xmx and -Xms) via JAVA_OPTS
2) isolate the JVM from OS signals (-Xrs) via JAVA_OPTS

Probably 2) is more likely, but that usually has a graceful shutdown. 1) might happen, but you usually just get out of memory messages in the JVM.

Hope that is of use.
Actions

Go to original post