This content has been marked as final. Show 2 replies
We've been using jboss 4.0.5.GA and we think we've found a bug with run.sh on Solaris (9 or 10).
This link is the patch that seems to have introduced this problem:
This link is where the patch was discussed:
To trigger the bug, you need to set LAUNCH_JBOSS_IN_BACKGROUND. Then start the jboss server normally. Once it's started stop the server. The JVM stops, however the run.sh script hangs around consuming 100% of a single CPUs resources.
The problem seems to be this bit of script, plus the fact that the script shebang is #!/bin/sh
while [ "$WAIT_STATUS" -ne 127 ]; do JBOSS_STATUS=$WAIT_STATUS wait $JBOSS_PID 2>/dev/null WAIT_STATUS=$? done
if [ -x /bin/wait ]; then alias wait='/bin/wait' fi