We use 2 ways to kill the server forcibly. Both will work with -Xrs
1) Runtime.halt()
2) kill -9 pid or taskkill /f/t/pid pid
On 10/30/2010 10:40 AM, Noah White wrote:
Right.. I was thinking in terms of how you intend to 'shoot'
the unresponsive process and if this involved a SIGQuit/SIGKill
then that might get filtered out?
Sent from my iPhone
-Xrs should not be a problem. It just screens out
signals.
Sent from my iPhone
Out of curiosity, how is this all going to play in an
environment where the -Xrs option has been added to the
cmd that starts the VM spawned by asadmin.bat and also
added to the JVM options in domain.xml to in order to
prevent the server from terminating on Windows when the
user whose process it is running under logs out of the
console session? Preventing that termination due to log
out is critical on Windows servers with glassfish running
as a service.
-Noah
On Fri, Oct 29, 2010 at 7:57
PM, Joe Di Pol
<joe.dipol@oracle.com>
wrote:
There's no "--force" for stop-local-instance is
there? Seems
like that would be a good place for this. It could
try to
stop the server gently, and if that didn't work
shoot it.
This would also give us the option to have
stop-instance
run "stop-local-instance --force" over SSH as a last
resort
for stubborn instances.
Joe
--
Byron Nevins - Oracle Corporation
Home: 650-359-1290
Cell: 650-784-4123
Sierra: 209-295-2188