Managed Server Not Restarted by Node Manager If "Server Lifecycle Timeout" Expires
Last updated on FEBRUARY 11, 2017
Applies to:Oracle WebLogic Server - Version 10.3.5 to 10.3.6
Information in this document applies to any platform.
In the context of Whole Server Migration, if the lease data source becomes unavailable, this will lead to the server transitioning to a FAILED status, and initiating a shutdown. If the shutdown completes, the Node Manager will restart it. So far, so good.
However, if for some reason, the shutdown process gets delayed or stalls so that the "Server LifeCycle Timeout" (that defaults to 30 seconds) expires, the managed server will interrupt the shutdown process and kill itself immediately.
Consequence: the Node Manager will interpret it as an intended shutdown and won't try to restart it, which means that the server restart won't happen.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms