-
Bug
-
Resolution: Done
-
Major
-
None
-
None
-
-
NEW
I was trying to test jboss_init_redhat.sh script to start and stop JBoss EAP as service with my local EAP 5.3 build. I found that once I started server and execute stop command, the server can not be stopped due to "No JBossas is currently running".
From the jboss_init_redhat.sh script code:
function procrunning() { procid=0 JBOSSSCRIPT=$(echo $JBOSSSH | awk '{print $1}' | sed 's/\//\\\//g') for procid in `/sbin/pidof -x "$JBOSSSCRIPT"`; do ps -fp $procid | grep "${JBOSSSH% *}" > /dev/null && pid=$procid done }
the sed regexp substitution changes the right path from
/home/wangchao/work/jbossas/EAP5/JBPAPP_5/build/output/jboss-5.3.0.Branch/bin/run.sh
to
\/home\/wangchao\/work\/jbossas\/EAP5\/JBPAPP_5\/build\/output\/jboss-5.3.0.Branch\/bin\/run.sh
therefore, it can't get to right procid to proceed to stop server.
- relates to
-
JBPAPP-3029 jboss_init_redhat script stop feature generates exception
- Closed