FAILED State

  • A running server instance can fail as a result of out-of-memory exceptions or stuck application threads, or if one or more critical services become dysfunctional. A server instance monitors its health, and upon detecting that one or more critical subsystems are unstable, it declares itself FAILED.
  • A FAILED server instance cannot satisfy administrative or client requests.
  • When a server instance enters the FAILED state, it attempts to return to a non-failed state. If it failed prior to reaching the ADMIN state, the server instance shuts itself down with an exit code that is less than zero. For information about server exit codes, see WebLogic Server Exit Codes and Restarting After Failure.
  • If the server instance fails after reaching the ADMIN state, but before reaching the RUNNING state, by default, it returns to the ADMIN state, if the administration port is enabled.

Note: If desired, you can configure a server instance that fails after reaching the ADMIN state, to shut itself down, rather than return to the ADMIN state

A server instance can enter the FAILED state from any other state. However, once a server instance has entered the FAILED state, it cannot return to a running state directly. The FAILED state is fatal and a server must go into the ADMIN or SHUTDOWN state before returning to the RUNNING state.

Note: It is theortically possible that a server could become available again once the FAILED state is entered, for example if hung threads causing a failed state become unhung.

Note: However, once FAILED state is entered, a server must go into the ADMIN or SHUTDOWN states before returning to RUNNING.

Reference:

http://docs.oracle.com/cd/E11035_01/wls100/server_start/server_life.html