Why won't this command stop WAS?
WAS version 8.5.5.11 running CLM 6.0.4
|
One answer
I'm pretty sure if you remove the Windows service, you should be able to stop the process by the command. The message basically says that the WASService.exe command cannot attach to the WAS process (java.exe) due to certificate issues. The two processes are likely using different trust stores, and you will need to import the certificate from the WAS profile keystore, into the default trust store of the bundled JVM, particularly when you have replaced the WAS profile certificate. I haven't got time to tested it to give you the exact steps though.
Comments
Kevin Ramer
commented Sep 08 '17, 11:21 a.m.
I've seen this on interactive shutdown when a new SSL certificate was installed in the DefaultKeyStore. The stopServer offers the ability to add the certificate "on the spot" and if the certificate is confirmed, then future stopServer commands will not be hindered.
Donald Nong
commented Sep 14 '17, 12:14 a.m.
That's right, and I have seen it before. That's why I suggested removing the Windows service first - otherwise the task will be delegated to the Windows service (WASService.exe).
Will simply uninstalling and reinstalling the service solve this? Or do I need to also import a certificate? It is not prompting me to add a cert "on the spot", so can you tell me which keystore I add the certificate to?
Donald Nong
commented Sep 26 '17, 11:04 p.m.
Uninstalling the service does not necessarily "resolve" the issue, but it makes it interactive and easier to work with. If you don't get prompt to import the certificate on the spot, you can try to follow the instructions below.
Rafael Rodriguez Montes
commented May 01 '20, 8:10 p.m.
Hello is there a final resolution?
the links are broken, where and how do I sync the certs with the wndows service with WAS?
Rafael Rodriguez Montes
commented May 01 '20, 9:40 p.m.
I found the solution, remove it from windows services, start it without windows service and then try to stop it it will prompt to accept the certificate and after that you can hook it back in a windows service and should work.
thank you for all your help.
showing 5 of 6
show 1 more comments
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
What's the output of the command?
Running the command initially produces this response:
ADMU0116I: Tool information is being logged in file
C:\IBM\Websphere\AppServer\profiles\AppSrv01\logs\server1\stopServer.
log
ADMU7702I: Because server1 is registered to run as a Windows Service, the
request to stop this server will be completed by stopping the
associated Windows Service.
ADMU0116I: Tool information is being logged in file
C:\IBM\Websphere\AppServer\profiles\AppSrv01\logs\server1\stopServer.
log
ADMU0128I: Starting tool with the AppSrv01 profile
ADMU3100I: Reading configuration for server: server1
oh wow! I can finally upload image attachments!!
I need to attached the stopServer.log, not a screenshot of it.