A timeout error displays when starting the server immediately after a stop request is issued
Starting a WebSphere® Application Server immediately after a stop request is issued can result in a timeout error message; even if the status of the server in the Servers view displayed Stopped before you starting the server.
Server <server_name> was unable to start within <nnn> seconds. If the server requires more time, try increasing the timeout in the server editor.
Where
<server_name> is the name of the server in the
Servers view, and <nnn> is the number of seconds
specified in the Start control under the Timeouts section
of the server editor.Although the status of the server in the Servers view displays as Stopped, the server might not actually be stopped. If the server is on a slow processing machine or has a slow response time, more time is required to stop the server.
If the timeout error message displays, click OK and the server stops and starts completely. If you find the server is stopped and the Servers view does not reflect the same Stopped status, restart the development workbench.
However, when you want to restart a server that is already running and started, right-click the server in the Servers view and select Restart; instead of selecting Stop and immediately followed by a Start command. Selecting the Restart option gives control to the workbench to handle the changeover between the stop and start of the server.