Details
-
Bug
-
Resolution: Done
-
Minor
-
EAP 5.0.1
-
None
-
RHEL 6.0
It's a bash script so I'm not sure the java version and such are relavant
-
-
Workaround Exists
-
-
Low
-
On RHEL 6 the JBoss service script had some backslashes incorrectly escaped, resulting in an invalid command and stopping JBoss being started or stopped. The script has been fixed and JBoss can reliably be started and stopped on RHEL 6.
-
Documented as Resolved Issue
Description
I think the the service script for jbossas it trying to replace backslashes with forward slashes when it goes to get the pid of a runnin gprocess via tyhe run.sh script.
problem is that is adds backslashes into the path of run.sh instead of replacing them.
— jbossas.rpm_broken 2011-02-09 10:27:34.000000000 -0500
+++ jbossas 2011-02-09 10:27:42.000000000 -0500
-202,7 +202,7 @@
function procrunning() {
procid=0
- JBOSSSCRIPT=$(echo $JBOSS_HOME/bin/run.sh|sed 's/\//\\\//g')
+ JBOSSSCRIPT=$(echo $JBOSS_HOME/bin/run.sh|sed 's/\\/\//g')
for procid in `pidof -x "$JBOSSSCRIPT"`; do
if [ ! -z $JBOSS_IP ]; then