Suspended State
When an enterprise is in a
suspended
state:
-
Only read-only ActiveMatrix Administrator web services are available for use. That is, you cannot execute ActiveMatrix Administrator CLI or GUI requests which require a write to the system. For example, you cannot create a node. All other ActiveMatrix Administrator web services throw an exception that the enterprise is in a
suspended
state and some features are not available for use. - ActiveMatrix Administrator tasks or user actions cannot be executed.
- The runtime node does not process any lifecycle actions.
- There are no changes in the component state.
- All the nodes are in a
suspended
state.
The
suspended
state is transient in nature for all entities - SystemNode, runtime nodes and all hosts. Restarting any of these entities (allowed only from the tibcohost CLI) brings them out of the
suspended
state.
-
If an action is queued during the
suspended
state or while transiting to thesuspended
state, the action is resumed when the enterprise comes out of thesuspended
state.When an enterprise is in a
suspended
state, if a node is down, it is recommended that you keep the node down and not restart it. -
When an enterprise is in a
suspended
state, the nodes cannot be stopped through the ActiveMatrix Administrator UI or CLI scripts as the action is not a read operation. However, if you kill the SystemNode or stop the SystemNode usingtibcohost stopNodes
, thesuspended
status is removed from the enterprise but still valid for runtime nodes. To bring thesuspended
status of the enterprise in sync with the runtime node, run the following command:ant -f enterprise_suspend_build.xml suspend
- For a replicated setup, the suspended state must be used for both the primary ActiveMatrix Administrator and the replicated ActiveMatrix Administrator, and not just one of them.