This is the expected behavior. To get JBoss to start in the background, use the jboss_init_redhat.sh script, or a custom written one.
Thank you very much for your reply.
I set up the JBOSS_HOME path in the jboss_init_redhat.sh script and ran it, but this time nothing started. This was the output. I ran it with the "start" parameter.
[root@924 bin]# ./jboss_init_redhat.sh start
CMD_START = cd /usr/jboss-3.2.3_nukes-1.0.0/bin; /usr/jboss-3.2.3_nukes-1.0.0/bin/run.sh -c all
Do you have any suggestions on what I am missing here?
Frankly, the jboss_init_redhat.sh script sucks, and hasn't been upgraded in ages.
It had many problems, some of which were reported long ago:"[ 546360 ] jboss_init_redhat.sh fails"
"[ 420297 ] JBoss startup/shutdown for RedHat"
(420297 was the "oldest bug in the database" for a very long time, till it was just closed without a fix.)
Last summer, I migrated to a new box w RH9, from a RH7.2, and hacked a bunch on that script. what i came up with tested pretty well on both 7.2 & 9. But now I dont have 7.2 to test on anymore, and haven't had any recent time to put into it.
But after seeing your post here on Nukes, I went back and found my script work from last summer ... and cleaned it up a bit and submitted it as a patch:
912548 a cleanup and overhaul of jboss_init_redhat.sh 2004-03-09 02:58 nobody hxp
You can download it from:
(Look for "download" at the bottom of the page.)
You'll also find a very detailed explanation of the problems from the old script that you've been trying to use, so if you're curious, it probably will clear up some of the mysteries.
Nukes User is not really the best Forum thread for this... but why dont you take a look at it, try it out, and post your feedback here?
There is also a decent (probably needs some tweaking) script which will allow you to start multiple instances of jboss: