| Application
|
- Not Deployed - before an application is deployed.
- Deployed - after the first time the application is deployed.
- Partially Undeployed - while an application is being undeployed.
- Partially Running - the application is deployed to more than one node and not all the nodes are running.
- Starting
- Start Failed - click the
Action History link in the Administrator to get more information.
- Running
- Stopped - after the application has been started and stopped.
- Stopping
- Partially Stopped - the application's components and bindings are in different states.
- Uninstalling
- Partially Uninstalled - not all the components and bindings of the application have been uninstalled.
- Waiting for Dependencies - either a resource instance or application that this application depends upon is not running. Once all dependencies are running, the components which are waiting will automatically be started.
- Preparing for Undeploy - the application is waiting for process instances and work items to be completed.
Note: This is a normal state when undeploying an application and there are process instances or work items that are open. The application can remain in this state for a very long time, since completing the open work items involves manual intervention. When the work items are completed, the application will be automatically undeployed.
- Interrupted Preparing for Undeploy - indicates the application that was preparing for undeploy was either stopped, or its dependency taken away.
Note: An application may depend on other application processes. If any of the dependent applications are stopped or undeployed, it takes away a dependency for the main application. In such a situation, the main application will go into a state of
Interrupted Preparing for Undeploy and will no longer progress work or process instances. To recover from this state, you can either start the application or bring back the dependencies by starting the processes or deploying the dependant applications.
- Partially Ready for Undeploy - some components have completed processing and have been marked as ready for undeploy, but other components in the application have yet to complete processing.
- Unknown
- Lost contact - when a host has lost contact with the Administrator server.
Note: The runtime state is a roll-up value for all the application's components and bindings. Partial states mean that some of an application's components and bindings are in a different state than others.
|
| Feature
|
- Marked for Install - after a feature has been added to a node and before the change has been applied to runtime.
- Marked for Uninstall - after a feature is removed and before the change is applied to runtime.
- Installed - after a feature has been applied to runtime.
|
| Host
|
- Initializing
- Initializing Failed - click the
Action History link to get more information.
- Initialized
- Lost Contact - when the host has lost contact with the Administrator server.
- Starting
- Starting Failed - click the
Action History link to get more information.
- Running
- Stopping
- Stopped - when the host is explicitly stopped and has completed the shutdown process.
- Unknown
|
| Node
|
- Not Installed - after a node has been created and before is has been installed
- Not Running - after a node has been installed or when it was detected that the node ended without being stopped by the host. This applies when the process is detected as stopped.
- Stopping - Stopping a node is expected to be a quick activity. If the node is stuck at Stopping for more than a few minutes, checking the logs may indicate the problem.
- Stopped - the node was explicitly stopped. This is a normal and expected condition.
- Starting - Starting a node is expected to be a quick activity. If the node is stuck at Starting for more than a few minutes, checking the logs may indicate the problem.
- Start Failed - The host was not able to start the node process. Possible causes are that the
node_classpath.tra file contains errors, the JRE libraries are not found, or the OS is unable spawn additional processes. After this state ,the node is disabled and must be
manually enabled.
- Running
- Lost contact - When a host has lost contact with the Administrator server.
|
| Resource Instance
|
- Not Installed - after a resource instance has been added to a node and before it has been installed
- Running - after a resource instance has been installed and the node on which it has been installed is Running
- Uninstalled - either the resource instance is uninstalled or the node on which the resource instance is installed is Not Running
- Stopped - when a host has lost contact with the Administrator server.
|
