How to shutdown WAS for the CLM Jazz tools, when there are 2 instances of WAS running and Jazz server inaccessible ?
After Red Hat patching and System maintenance, we cannot access the PRD Jazz server : "This webpage is not available", we found:
-
Two instances of WAS running on the host in PRD
root 2766 2628 0 Mar01 ? 00:00:16 /opt/IBM/WebSphere/java/bin/java -Dosgi.install.area=/opt/IBM/WebSphere -Dosgi.configuration.area=/......
root 4160 2766 0 Mar01 ? 00:07:33 /opt/IBM/WebSphere/java/bin/java -Declipse.security -Dwas.status.socket=<#####> -Dosgi.install.area=/.......
where <#####> is actual number blanked out.
- The shutdown script would fail
- A reboot failed, apparently because the shutdown script failed.
- Note that WAS was not running on DEV server, which went through the same maintenance, and it was restarted OK.
What should we do to restore normalcy.
Is it safe to kill the top process then try the shutdown script ? or both processes ?
Accepted answer
Try
sudo kill -9 2766
Comments
That was what I have been tempted to do since last night, but is it safe (I am not familiar with WAS server side yet) ? Is it safer than a reboot of the host (maybe SysAdmin can force a successfull reboot) ?
Thanks Krzysztof, BTW!
Hi Long,
I don't know any better option to stop your server if WAS console is not responding. Even if that might happen any issues, you do not have many more options here :/
Thanks Krzysztof. :) :(
Comments
N Z
Mar 03 '14, 4:08 p.m.Sometimes you have to use kill -9, but only as a last resort. A couple of things you could try to minimise any potential problems before taking this step:
long TRUONG
Mar 03 '14, 5:34 p.m.Thanks NZ
Krzysztof Kaźmierczyk
Mar 04 '14, 2:45 a.m.Hi Long,
Did it happen first time? Or it is happening regularly? If it happens regularly, then I receommend you creating new PMR for CLM support.
long TRUONG
Mar 04 '14, 7:34 a.m.This is first time since I was brought in to admin the Jazz tools.