11:58 p.m.
run.sh can consume 100% single CPU resources on Solaris
-------------------------------------------------------
Key: JBAS-4287
URL: http://jira.jboss.com/jira/browse/JBAS-4287
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Other
Affects Versions: JBossAS-4.0.5.GA
Environment: Solaris on SPARC (version 9 & 10)
Reporter: Quenten Alick
When shutting down jboss the run.sh script remain alive and consumes 100% of a single CPUs
resources. run.sh needs to be killed off.
To trigger the bug, you need to
1) set LAUNCH_JBOSS_IN_BACKGROUND
2) start the jboss server normally
3) Once it's started stop the server
At this point the JVM stops, however the run.sh script remains running 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
On Solaris, /bin/sh is *real* bourne shell and the wait shell-built-in for /bin/sh on
Solaris returns 0 (not 127) if the PID (passed as an argument) doesn't exist. The man
page for wait states that this is the correct behaviour. Therefore wait returns 0 and the
while loop continues forever burning up CPU resources (until you kill it with one of the
signals not being trapped).
Here's a link to the patch that may have introduced the bug.
http://jira.jboss.com/jira/browse/JBAS-3748
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:31 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-4287) run.sh can consume 100% single CPU resources on Solaris
[ http://jira.jboss.com/jira/browse/JBAS-4287?page=comments#action_12360099 ]
Ian Springer commented on JBAS-4287:
------------------------------------
The first suggested fix (changing the shebang to /bin/bash) is not a portable option,
because /bin/bash will not exist on many non-Linux UNIX systems. I do like the second
suggested fix (aliasing wait to /bin/wait if /bin/wait exists). I'll attach a patch
that implements the alias fix.
run.sh can consume 100% single CPU resources on Solaris
-------------------------------------------------------
Key: JBAS-4287
URL: http://jira.jboss.com/jira/browse/JBAS-4287
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-4.0.5.GA
Environment: Solaris on SPARC (version 9 & 10)
Reporter: Quenten Alick
When shutting down jboss the run.sh script remain alive and consumes 100% of a single
CPUs resources. run.sh needs to be killed off.
To trigger the bug, you need to
1) set LAUNCH_JBOSS_IN_BACKGROUND
2) start the jboss server normally
3) Once it's started stop the server
At this point the JVM stops, however the run.sh script remains running 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
On Solaris, /bin/sh is *real* bourne shell and the wait shell-built-in for /bin/sh on
Solaris returns 0 (not 127) if the PID (passed as an argument) doesn't exist. The man
page for wait states that this is the correct behaviour. Therefore wait returns 0 and the
while loop continues forever burning up CPU resources (until you kill it with one of the
signals not being trapped).
Here's a link to the patch that may have introduced the bug.
http://jira.jboss.com/jira/browse/JBAS-3748
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:19 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-4287) run.sh can consume 100% single CPU resources on Solaris
[ http://jira.jboss.com/jira/browse/JBAS-4287?page=all ]
Ian Springer updated JBAS-4287:
-------------------------------
Attachment: run.sh.patch
It turns out the /bin/wait alias was not a viable solution. Based on my testing on a
Solaris 9 box, Solaris' /bin/sh does not have a wait builtin, so it is using
/usr/bin/wait (or whatever wait is in the PATH) by default. And /usr/bin/wait and
/bin/wait are both shell scripts that delegate to ksh's wait builtin, which apparently
does not support the 127 exit status for non-existent processes. So it looks like the best
way to go here is to remove the -ne 127 check and the while loop altogether. I've
attached a patch to that effect. I have tested it under Cygwin.
run.sh can consume 100% single CPU resources on Solaris
-------------------------------------------------------
Key: JBAS-4287
URL: http://jira.jboss.com/jira/browse/JBAS-4287
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-4.0.5.GA
Environment: Solaris on SPARC (version 9 & 10)
Reporter: Quenten Alick
Attachments: run.sh.patch
When shutting down jboss the run.sh script remain alive and consumes 100% of a single
CPUs resources. run.sh needs to be killed off.
To trigger the bug, you need to
1) set LAUNCH_JBOSS_IN_BACKGROUND
2) start the jboss server normally
3) Once it's started stop the server
At this point the JVM stops, however the run.sh script remains running 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
On Solaris, /bin/sh is *real* bourne shell and the wait shell-built-in for /bin/sh on
Solaris returns 0 (not 127) if the PID (passed as an argument) doesn't exist. The man
page for wait states that this is the correct behaviour. Therefore wait returns 0 and the
while loop continues forever burning up CPU resources (until you kill it with one of the
signals not being trapped).
Here's a link to the patch that may have introduced the bug.
http://jira.jboss.com/jira/browse/JBAS-3748
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:21 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-4287) run.sh can consume 100% single CPU resources on Solaris
[ http://jira.jboss.com/jira/browse/JBAS-4287?page=all ]
Ian Springer updated JBAS-4287:
-------------------------------
Attachment: run.sh
Here's the updated script. Would the reporter please try it out on his Solaris setup?
Thanks.
run.sh can consume 100% single CPU resources on Solaris
-------------------------------------------------------
Key: JBAS-4287
URL: http://jira.jboss.com/jira/browse/JBAS-4287
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-4.0.5.GA
Environment: Solaris on SPARC (version 9 & 10)
Reporter: Quenten Alick
Attachments: run.sh, run.sh.patch
When shutting down jboss the run.sh script remain alive and consumes 100% of a single
CPUs resources. run.sh needs to be killed off.
To trigger the bug, you need to
1) set LAUNCH_JBOSS_IN_BACKGROUND
2) start the jboss server normally
3) Once it's started stop the server
At this point the JVM stops, however the run.sh script remains running 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
On Solaris, /bin/sh is *real* bourne shell and the wait shell-built-in for /bin/sh on
Solaris returns 0 (not 127) if the PID (passed as an argument) doesn't exist. The man
page for wait states that this is the correct behaviour. Therefore wait returns 0 and the
while loop continues forever burning up CPU resources (until you kill it with one of the
signals not being trapped).
Here's a link to the patch that may have introduced the bug.
http://jira.jboss.com/jira/browse/JBAS-3748
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:21 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-4287) run.sh can consume 100% single CPU resources on Solaris
[ http://jira.jboss.com/jira/browse/JBAS-4287?page=comments#action_12360172 ]
Quenten Alick commented on JBAS-4287:
-------------------------------------
Thanks Ian. I've tried the patch on Solaris (SPARC) 8, 9 & 10 and it worked fine,
run.sh behaved perfectly.
run.sh can consume 100% single CPU resources on Solaris
-------------------------------------------------------
Key: JBAS-4287
URL: http://jira.jboss.com/jira/browse/JBAS-4287
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-4.0.5.GA
Environment: Solaris on SPARC (version 9 & 10)
Reporter: Quenten Alick
Attachments: run.sh, run.sh.patch
When shutting down jboss the run.sh script remain alive and consumes 100% of a single
CPUs resources. run.sh needs to be killed off.
To trigger the bug, you need to
1) set LAUNCH_JBOSS_IN_BACKGROUND
2) start the jboss server normally
3) Once it's started stop the server
At this point the JVM stops, however the run.sh script remains running 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
On Solaris, /bin/sh is *real* bourne shell and the wait shell-built-in for /bin/sh on
Solaris returns 0 (not 127) if the PID (passed as an argument) doesn't exist. The man
page for wait states that this is the correct behaviour. Therefore wait returns 0 and the
while loop continues forever burning up CPU resources (until you kill it with one of the
signals not being trapped).
Here's a link to the patch that may have introduced the bug.
http://jira.jboss.com/jira/browse/JBAS-3748
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:54 a.m.
New subject: [JBoss JIRA] Updated: (JBAS-4287) run.sh can consume 100% single CPU resources on Solaris
[ http://jira.jboss.com/jira/browse/JBAS-4287?page=all ]
Dimitris Andreadis updated JBAS-4287:
-------------------------------------
Fix Version/s: JBossAS-4.2.0.GA
Evaluate for 4.2.0.GA.
run.sh can consume 100% single CPU resources on Solaris
-------------------------------------------------------
Key: JBAS-4287
URL: http://jira.jboss.com/jira/browse/JBAS-4287
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-4.0.5.GA
Environment: Solaris on SPARC (version 9 & 10)
Reporter: Quenten Alick
Fix For: JBossAS-4.2.0.GA
Attachments: run.sh, run.sh.patch
When shutting down jboss the run.sh script remain alive and consumes 100% of a single
CPUs resources. run.sh needs to be killed off.
To trigger the bug, you need to
1) set LAUNCH_JBOSS_IN_BACKGROUND
2) start the jboss server normally
3) Once it's started stop the server
At this point the JVM stops, however the run.sh script remains running 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
On Solaris, /bin/sh is *real* bourne shell and the wait shell-built-in for /bin/sh on
Solaris returns 0 (not 127) if the PID (passed as an argument) doesn't exist. The man
page for wait states that this is the correct behaviour. Therefore wait returns 0 and the
while loop continues forever burning up CPU resources (until you kill it with one of the
signals not being trapped).
Here's a link to the patch that may have introduced the bug.
http://jira.jboss.com/jira/browse/JBAS-3748
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:17 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-4287) run.sh can consume 100% single CPU resources on Solaris
[ http://jira.jboss.com/jira/browse/JBAS-4287?page=comments#action_12361176 ]
Dimitris Andreadis commented on JBAS-4287:
------------------------------------------
Can you guys comment on leaving out the while loop in the patch?
Executing this on Cygwin with some extra logging resulst in 3 times the
"Waiting..." message appearing. One initially and 2 more times when I send e.g.
a SIGTERM to run.sh, so that makes me think the while do is there for a purpose.
echo "Before the loop"
WAIT_STATUS=0
while [ "$WAIT_STATUS" -ne 127 ]; do
JBOSS_STATUS=$WAIT_STATUS
echo "Waiting..."
wait $JBOSS_PID 2>/dev/null
WAIT_STATUS=$?
done
run.sh can consume 100% single CPU resources on Solaris
-------------------------------------------------------
Key: JBAS-4287
URL: http://jira.jboss.com/jira/browse/JBAS-4287
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-4.0.5.GA
Environment: Solaris on SPARC (version 9 & 10)
Reporter: Quenten Alick
Fix For: JBossAS-4.2.0.GA
Attachments: run.sh, run.sh.patch
When shutting down jboss the run.sh script remain alive and consumes 100% of a single
CPUs resources. run.sh needs to be killed off.
To trigger the bug, you need to
1) set LAUNCH_JBOSS_IN_BACKGROUND
2) start the jboss server normally
3) Once it's started stop the server
At this point the JVM stops, however the run.sh script remains running 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
On Solaris, /bin/sh is *real* bourne shell and the wait shell-built-in for /bin/sh on
Solaris returns 0 (not 127) if the PID (passed as an argument) doesn't exist. The man
page for wait states that this is the correct behaviour. Therefore wait returns 0 and the
while loop continues forever burning up CPU resources (until you kill it with one of the
signals not being trapped).
Here's a link to the patch that may have introduced the bug.
http://jira.jboss.com/jira/browse/JBAS-3748
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:08 p.m.
New subject: [JBoss JIRA] Assigned: (JBAS-4287) run.sh can consume 100% single CPU resources on Solaris
[ http://jira.jboss.com/jira/browse/JBAS-4287?page=all ]
Dimitris Andreadis reassigned JBAS-4287:
----------------------------------------
Assignee: Dimitris Andreadis
run.sh can consume 100% single CPU resources on Solaris
-------------------------------------------------------
Key: JBAS-4287
URL: http://jira.jboss.com/jira/browse/JBAS-4287
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-4.0.5.GA
Environment: Solaris on SPARC (version 9 & 10)
Reporter: Quenten Alick
Assigned To: Dimitris Andreadis
Fix For: JBossAS-4.2.0.GA
Attachments: run.sh, run.sh.patch
When shutting down jboss the run.sh script remain alive and consumes 100% of a single
CPUs resources. run.sh needs to be killed off.
To trigger the bug, you need to
1) set LAUNCH_JBOSS_IN_BACKGROUND
2) start the jboss server normally
3) Once it's started stop the server
At this point the JVM stops, however the run.sh script remains running 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
On Solaris, /bin/sh is *real* bourne shell and the wait shell-built-in for /bin/sh on
Solaris returns 0 (not 127) if the PID (passed as an argument) doesn't exist. The man
page for wait states that this is the correct behaviour. Therefore wait returns 0 and the
while loop continues forever burning up CPU resources (until you kill it with one of the
signals not being trapped).
Here's a link to the patch that may have introduced the bug.
http://jira.jboss.com/jira/browse/JBAS-3748
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:37 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-4287) run.sh can consume 100% single CPU resources on Solaris
[ http://jira.jboss.com/jira/browse/JBAS-4287?page=comments#action_12361210 ]
Ian Springer commented on JBAS-4287:
------------------------------------
Yeah, I did put that while loop in there for some purpose. I think it was needed for a
certain use case on either Cygwin or Linux, but I don't recall what that use case was.
Let me play around a bit later today or tomorrow. How soon do you need an answer?
run.sh can consume 100% single CPU resources on Solaris
-------------------------------------------------------
Key: JBAS-4287
URL: http://jira.jboss.com/jira/browse/JBAS-4287
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-4.0.5.GA
Environment: Solaris on SPARC (version 9 & 10)
Reporter: Quenten Alick
Assigned To: Dimitris Andreadis
Fix For: JBossAS-4.2.0.GA
Attachments: run.sh, run.sh.patch
When shutting down jboss the run.sh script remain alive and consumes 100% of a single
CPUs resources. run.sh needs to be killed off.
To trigger the bug, you need to
1) set LAUNCH_JBOSS_IN_BACKGROUND
2) start the jboss server normally
3) Once it's started stop the server
At this point the JVM stops, however the run.sh script remains running 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
On Solaris, /bin/sh is *real* bourne shell and the wait shell-built-in for /bin/sh on
Solaris returns 0 (not 127) if the PID (passed as an argument) doesn't exist. The man
page for wait states that this is the correct behaviour. Therefore wait returns 0 and the
while loop continues forever burning up CPU resources (until you kill it with one of the
signals not being trapped).
Here's a link to the patch that may have introduced the bug.
http://jira.jboss.com/jira/browse/JBAS-3748
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:20 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-4287) run.sh can consume 100% single CPU resources on Solaris
[ http://jira.jboss.com/jira/browse/JBAS-4287?page=comments#action_12361265 ]
Dimitris Andreadis commented on JBAS-4287:
------------------------------------------
It has to be today or tomorrow the very latest to have a chance to make it for 4.2.0.GA
run.sh can consume 100% single CPU resources on Solaris
-------------------------------------------------------
Key: JBAS-4287
URL: http://jira.jboss.com/jira/browse/JBAS-4287
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-4.0.5.GA
Environment: Solaris on SPARC (version 9 & 10)
Reporter: Quenten Alick
Assigned To: Dimitris Andreadis
Fix For: JBossAS-4.2.0.GA
Attachments: run.sh, run.sh.patch
When shutting down jboss the run.sh script remain alive and consumes 100% of a single
CPUs resources. run.sh needs to be killed off.
To trigger the bug, you need to
1) set LAUNCH_JBOSS_IN_BACKGROUND
2) start the jboss server normally
3) Once it's started stop the server
At this point the JVM stops, however the run.sh script remains running 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
On Solaris, /bin/sh is *real* bourne shell and the wait shell-built-in for /bin/sh on
Solaris returns 0 (not 127) if the PID (passed as an argument) doesn't exist. The man
page for wait states that this is the correct behaviour. Therefore wait returns 0 and the
while loop continues forever burning up CPU resources (until you kill it with one of the
signals not being trapped).
Here's a link to the patch that may have introduced the bug.
http://jira.jboss.com/jira/browse/JBAS-3748
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:31 a.m.
New subject: [JBoss JIRA] Commented: (JBAS-4287) run.sh can consume 100% single CPU resources on Solaris
[ http://jira.jboss.com/jira/browse/JBAS-4287?page=comments#action_12361276 ]
Dimitris Andreadis commented on JBAS-4287:
------------------------------------------
Also, do you happen to know what signal is generated when you ctrl-c on cygwin?
run.sh can consume 100% single CPU resources on Solaris
-------------------------------------------------------
Key: JBAS-4287
URL: http://jira.jboss.com/jira/browse/JBAS-4287
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-4.0.5.GA
Environment: Solaris on SPARC (version 9 & 10)
Reporter: Quenten Alick
Assigned To: Dimitris Andreadis
Fix For: JBossAS-4.2.0.GA
Attachments: run.sh, run.sh.patch
When shutting down jboss the run.sh script remain alive and consumes 100% of a single
CPUs resources. run.sh needs to be killed off.
To trigger the bug, you need to
1) set LAUNCH_JBOSS_IN_BACKGROUND
2) start the jboss server normally
3) Once it's started stop the server
At this point the JVM stops, however the run.sh script remains running 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
On Solaris, /bin/sh is *real* bourne shell and the wait shell-built-in for /bin/sh on
Solaris returns 0 (not 127) if the PID (passed as an argument) doesn't exist. The man
page for wait states that this is the correct behaviour. Therefore wait returns 0 and the
while loop continues forever burning up CPU resources (until you kill it with one of the
signals not being trapped).
Here's a link to the patch that may have introduced the bug.
http://jira.jboss.com/jira/browse/JBAS-3748
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-4287) run.sh can consume 100% single CPU resources on Solaris
[ http://jira.jboss.com/jira/browse/JBAS-4287?page=all ]
Dimitris Andreadis updated JBAS-4287:
-------------------------------------
Fix Version/s: JBossAS-4.2.1.CR1
(was: JBossAS-4.2.0.GA)
Next release.
run.sh can consume 100% single CPU resources on Solaris
-------------------------------------------------------
Key: JBAS-4287
URL: http://jira.jboss.com/jira/browse/JBAS-4287
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-4.0.5.GA
Environment: Solaris on SPARC (version 9 & 10)
Reporter: Quenten Alick
Assigned To: Dimitris Andreadis
Fix For: JBossAS-4.2.1.CR1
Attachments: run.sh, run.sh.patch
When shutting down jboss the run.sh script remain alive and consumes 100% of a single
CPUs resources. run.sh needs to be killed off.
To trigger the bug, you need to
1) set LAUNCH_JBOSS_IN_BACKGROUND
2) start the jboss server normally
3) Once it's started stop the server
At this point the JVM stops, however the run.sh script remains running 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
On Solaris, /bin/sh is *real* bourne shell and the wait shell-built-in for /bin/sh on
Solaris returns 0 (not 127) if the PID (passed as an argument) doesn't exist. The man
page for wait states that this is the correct behaviour. Therefore wait returns 0 and the
while loop continues forever burning up CPU resources (until you kill it with one of the
signals not being trapped).
Here's a link to the patch that may have introduced the bug.
http://jira.jboss.com/jira/browse/JBAS-3748
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:55 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-4287) run.sh can consume 100% single CPU resources on Solaris
[ http://jira.jboss.com/jira/browse/JBAS-4287?page=comments#action_12418889 ]
Jonas Grote commented on JBAS-4287:
-----------------------------------
Same on Ubuntu Linux Hoary, where /bin/sh is a dash shell.
Removing the loop works, as well as adding a "sleep 1" to the loop. Only found
out the latter while trying to debug.
I post here because in the current version it seems to be the same run.sh including the
while loop.
run.sh can consume 100% single CPU resources on Solaris
-------------------------------------------------------
Key: JBAS-4287
URL: http://jira.jboss.com/jira/browse/JBAS-4287
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-4.0.5.GA
Environment: Solaris on SPARC (version 9 & 10)
Reporter: Quenten Alick
Assigned To: Dimitris Andreadis
Attachments: run.sh, run.sh.patch
When shutting down jboss the run.sh script remain alive and consumes 100% of a single
CPUs resources. run.sh needs to be killed off.
To trigger the bug, you need to
1) set LAUNCH_JBOSS_IN_BACKGROUND
2) start the jboss server normally
3) Once it's started stop the server
At this point the JVM stops, however the run.sh script remains running 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
On Solaris, /bin/sh is *real* bourne shell and the wait shell-built-in for /bin/sh on
Solaris returns 0 (not 127) if the PID (passed as an argument) doesn't exist. The man
page for wait states that this is the correct behaviour. Therefore wait returns 0 and the
while loop continues forever burning up CPU resources (until you kill it with one of the
signals not being trapped).
Here's a link to the patch that may have introduced the bug.
http://jira.jboss.com/jira/browse/JBAS-3748
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:03 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-4287) run.sh can consume 100% single CPU resources on Solaris
[ http://jira.jboss.com/jira/browse/JBAS-4287?page=all ]
Dimitris Andreadis updated JBAS-4287:
-------------------------------------
Fix Version/s: JBossAS-4.2.3.GA
run.sh can consume 100% single CPU resources on Solaris
-------------------------------------------------------
Key: JBAS-4287
URL: http://jira.jboss.com/jira/browse/JBAS-4287
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-4.0.5.GA
Environment: Solaris on SPARC (version 9 & 10)
Reporter: Quenten Alick
Assigned To: Dimitris Andreadis
Fix For: JBossAS-4.2.3.GA
Attachments: run.sh, run.sh.patch
When shutting down jboss the run.sh script remain alive and consumes 100% of a single
CPUs resources. run.sh needs to be killed off.
To trigger the bug, you need to
1) set LAUNCH_JBOSS_IN_BACKGROUND
2) start the jboss server normally
3) Once it's started stop the server
At this point the JVM stops, however the run.sh script remains running 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
On Solaris, /bin/sh is *real* bourne shell and the wait shell-built-in for /bin/sh on
Solaris returns 0 (not 127) if the PID (passed as an argument) doesn't exist. The man
page for wait states that this is the correct behaviour. Therefore wait returns 0 and the
while loop continues forever burning up CPU resources (until you kill it with one of the
signals not being trapped).
Here's a link to the patch that may have introduced the bug.
http://jira.jboss.com/jira/browse/JBAS-3748
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:13 p.m.
New subject: [JBoss JIRA] Commented: (JBAS-4287) run.sh can consume 100% single CPU resources on Solaris
[ http://jira.jboss.com/jira/browse/JBAS-4287?page=comments#action_12418930 ]
Ian Springer commented on JBAS-4287:
------------------------------------
Also, do you happen to know what signal is generated when you ctrl-c
on cygwin?
I'm pretty sure Ctrl-C sends a SIGINT. I did find some threads that talk about issues
w/ Ctrl-C under Cygwin that can occur when the CYGWIN environment variable is set to
"tty" in the Cygwin process (e.g. see
http://lists.osuosl.org/pipermail/darcs-users/2006-December/010717.html). Perhaps you were
encountering that issue?
run.sh can consume 100% single CPU resources on Solaris
-------------------------------------------------------
Key: JBAS-4287
URL: http://jira.jboss.com/jira/browse/JBAS-4287
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-4.0.5.GA
Environment: Solaris on SPARC (version 9 & 10)
Reporter: Quenten Alick
Assigned To: Dimitris Andreadis
Fix For: JBossAS-4.2.3.GA
Attachments: run.sh, run.sh.patch
When shutting down jboss the run.sh script remain alive and consumes 100% of a single
CPUs resources. run.sh needs to be killed off.
To trigger the bug, you need to
1) set LAUNCH_JBOSS_IN_BACKGROUND
2) start the jboss server normally
3) Once it's started stop the server
At this point the JVM stops, however the run.sh script remains running 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
On Solaris, /bin/sh is *real* bourne shell and the wait shell-built-in for /bin/sh on
Solaris returns 0 (not 127) if the PID (passed as an argument) doesn't exist. The man
page for wait states that this is the correct behaviour. Therefore wait returns 0 and the
while loop continues forever burning up CPU resources (until you kill it with one of the
signals not being trapped).
Here's a link to the patch that may have introduced the bug.
http://jira.jboss.com/jira/browse/JBAS-3748
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:04 p.m.
New subject: [JBoss JIRA] Updated: (JBAS-4287) run.sh can consume 100% single CPU resources on Solaris
[ http://jira.jboss.com/jira/browse/JBAS-4287?page=all ]
Ian Springer updated JBAS-4287:
-------------------------------
Attachment: JBAS-4287.patch
The attached patch (JBAS-4287.patch) should fix the infinite loop issue on Solaris, as
well as when /bin/sh is linked to dash (e.g. on Ubuntu).
The new wait-for-exit code looks like this:
# Wait until the background process exits
WAIT_STATUS=128
while [ "$WAIT_STATUS" -ge 128 ]; do
wait $JBOSS_PID 2>/dev/null
WAIT_STATUS=$?
if [ "${WAIT_STATUS}" -gt 128 ]; then
SIGNAL=`expr ${WAIT_STATUS} - 128`
SIGNAL_NAME=`kill -l ${SIGNAL}`
echo "*** JBossAS process (${JBOSS_PID}) received ${SIGNAL_NAME} signal.
***" >&2
fi
done
if [ "${WAIT_STATUS}" -lt 127 ]; then
JBOSS_STATUS=$WAIT_STATUS
else
JBOSS_STATUS=0
fi
This new while loop covers the different variations of the wait command:
1) bash on Linux: when the bash run.sh process receives a termination signal, 1st call to
wait returns an exit status >128 that represents the signal received, 2nd call to wait
returns the exit status of the JBoss process itself (typically 0)
2) dash on Linux: same as above. NOTE: as an earlier comment in this issue described,
dash's wait will infinitely return 0, even after the JBossAS process has exited (it
should return 127 once the process no longer exists), unless a sleep is added to the loop.
this is no longer an issue, since the loop's condition has been changed so the loop
will terminate on any wait status <128
3) bash on CygWin: when the bash run.sh process receives a termination signal, 1st call to
wait returns an exit status >128 that represents the signal *the bash process* received
(I believe this is a bug in CygWin bash), 2nd call to wait returns an exit status >128
that represents the signal *the JBossAS process* received, 3rd call to wait returns the
exit status of the JBoss process itself (typically 0)
4) sh on Solaris: 1st call to wait returns the exit status of the JBoss process itself
(typically 0)
I've tested all of the above environments. It would be good if someone else could test
on HP-UX and AIX.
run.sh can consume 100% single CPU resources on Solaris
-------------------------------------------------------
Key: JBAS-4287
URL: http://jira.jboss.com/jira/browse/JBAS-4287
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-4.0.5.GA
Environment: Solaris on SPARC (version 9 & 10)
Reporter: Quenten Alick
Assigned To: Dimitris Andreadis
Fix For: JBossAS-4.2.3.GA
Attachments: JBAS-4287.patch, run.sh, run.sh.patch
When shutting down jboss the run.sh script remain alive and consumes 100% of a single
CPUs resources. run.sh needs to be killed off.
To trigger the bug, you need to
1) set LAUNCH_JBOSS_IN_BACKGROUND
2) start the jboss server normally
3) Once it's started stop the server
At this point the JVM stops, however the run.sh script remains running 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
On Solaris, /bin/sh is *real* bourne shell and the wait shell-built-in for /bin/sh on
Solaris returns 0 (not 127) if the PID (passed as an argument) doesn't exist. The man
page for wait states that this is the correct behaviour. Therefore wait returns 0 and the
while loop continues forever burning up CPU resources (until you kill it with one of the
signals not being trapped).
Here's a link to the patch that may have introduced the bug.
http://jira.jboss.com/jira/browse/JBAS-3748
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:49 p.m.
New subject: [JBoss JIRA] Closed: (JBAS-4287) run.sh can consume 100% single CPU resources on Solaris
[ http://jira.jboss.com/jira/browse/JBAS-4287?page=all ]
Dimitris Andreadis closed JBAS-4287.
------------------------------------
Fix Version/s: JBossAS-5.0.0.CR2
Resolution: Done
Suggested patch applied. Thanks a lot Ian!
run.sh can consume 100% single CPU resources on Solaris
-------------------------------------------------------
Key: JBAS-4287
URL: http://jira.jboss.com/jira/browse/JBAS-4287
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Other
Affects Versions: JBossAS-4.0.5.GA
Environment: Solaris on SPARC (version 9 & 10)
Reporter: Quenten Alick
Assigned To: Dimitris Andreadis
Fix For: JBossAS-4.2.3.GA, JBossAS-5.0.0.CR2
Attachments: JBAS-4287.patch, run.sh, run.sh.patch
When shutting down jboss the run.sh script remain alive and consumes 100% of a single
CPUs resources. run.sh needs to be killed off.
To trigger the bug, you need to
1) set LAUNCH_JBOSS_IN_BACKGROUND
2) start the jboss server normally
3) Once it's started stop the server
At this point the JVM stops, however the run.sh script remains running 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
On Solaris, /bin/sh is *real* bourne shell and the wait shell-built-in for /bin/sh on
Solaris returns 0 (not 127) if the PID (passed as an argument) doesn't exist. The man
page for wait states that this is the correct behaviour. Therefore wait returns 0 and the
while loop continues forever burning up CPU resources (until you kill it with one of the
signals not being trapped).
Here's a link to the patch that may have introduced the bug.
http://jira.jboss.com/jira/browse/JBAS-3748
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5910
days inactive
6380
days old
16 comments
4 participants
participants (4)
-
Dimitris Andreadis (JIRA) -
Ian Springer (JIRA)
-
Jonas Grote (JIRA)
-
Quenten Alick (JIRA)