Skip to content

After a server reboot on Windows, the IFS MWS-related Windows services are configured to start 'Automatically' but the Node Manager and other MWS services still don't come up on their own — is this expected, or a misconfiguration?

Answer

This is expected behavior tied to how the servers were shut down before the reboot, not a misconfiguration. If the IFS server components were shut down gracefully beforehand (using mws-svr.cmd, as recommended), WebLogic deliberately won't try to bring them back up automatically after the Windows service itself starts — a graceful shutdown is treated as an administrator's intentional stop, so WebLogic waits for an administrator to explicitly restart the components rather than assuming they should always come back. Only an abrupt/ungraceful shutdown (skipping mws-svr.cmd) causes the Windows service to attempt restarting the servers and components automatically based on their last known state — and that path isn't guaranteed to succeed cleanly anyway. The recommended practice is still to always gracefully shut down via mws-svr.cmd before a planned reboot, and then plan for a manual startup afterward as the expected, by-design behavior.

← Browse Developer Studio, deployment, and upgrades questions