I've been running into issues recently with the various WAS start and stop scripts (startManager/stopManager, startNode/stopNode, startServer/stopServer) apparently failing to perform their intended tasks. I have a good idea how long the operations should take in my lab environment, and I'll see the scripts hang while waiting for status. In all cases I've seen, the desired action actually does complete (servers are started/stopped), but the signal back to the script never occurs. Before thinking you have a real problem, it's worth a quick sanity check to make sure you don't have this type of scenario.
Look for the following signs:
- If you are running a start script, check for the "open for e-business" line in SystemOut.log. If it's there, the server is up and running
- If you are running a stop script, check for the "WSVR0024I: Server <server> stopped" line in SystemOut.log. If it's there, the server should be shut down. Double check by looking at your count of java.exe processes. The script to stop the server will invoke a new java.exe process, so if you have one server running on a system, there will be two java.exe processes. Once that count drops to one, it is just the process associated with the script that remains. It should also have a very low memory allocation
Once you identify that the desired action was performed, you can simply terminate the script by running Ctrl + C. I haven't identified a root cause for why this happens, but the workaround is easy enough that I've been able to live with it.
Chad Scott, IBM Connections, Software Support Engineer