Viewing AppNode Statuses

An AppNode has two states: Deployment and Runtime.

The Deployment state can have the following statuses:
AppNode Deployment Statuses
Status Description
In-Sync AppNode is in a synchronized state with deployment features, configurations, or both.
Out-of-Sync AppNode is out of synchronization with certain deployment features, configurations, or both.
An AppNode's Runtime state relies on the timestamp of the hosting machine and on the timestamp of the machine hosting the bwagent. The timestamps on the machines must be within 20 seconds of each other for the status of the AppNode to be reported correctly. The Runtime state can have the following statuses:
AppNode Runtime Statuses
Status Operations Allowed When in This Status Description
Running Stop Reported only by the AppNode.

The AppNode has successfully initialized all the product bundles and reached the target start level.

Stopped Start, Delete The AppNode is not running. This is determined only by the bwagent.
Deploying <none> This is a transitional state when an application is getting deployed on an AppSpace.
Impaired Stop The AppNode is in an Impaired state after it has encountered an error during the startup in one of the product bundles. This means that the application is not yet ready to run, and may impact the functionality of the AppNode.

Each application has a list of dependencies that need to be satisfied for it to run. These dependencies are listed below:

  • The engine must be up and running. If the engine is configured incorrectly, it might not start.
  • Shared resources that are defined in the application must be initialized. If shared resources are misconfigured, they might not start.
  • All bundles that belong to an application must be resolved. If a bundle is missing an import-package, it might not start.

If any of these dependencies are not met, the application is displayed as being in the Impaired state. The "la", which stands for list applications, command of the OSGi console shows the details of the application and their resolved and unresolved dependencies. This will explicitly tell you the dependency that is not met and where to look further to investigate the problem.

Unreachable <none> The AppNode is unreachable when a remote bwagent and the remote machine is down, or a network failure occurs resulting in network partitioning.

This state is determined only by the bwagent.

Start Failed Start, Delete This is determined by the bwagent when it is making an attempt to start the AppNode process when the AppNode does not start.
Starting Stop This is a transitional state reported by the AppNode when the Web API layer has been initialized, but the Web API is still accessible and can report the state.

This happens when a bundle blocks the shutdown thread.

Stopping <none> This is a transitional state when an AppNode stops gracefully or is forcefully shut down from the Admin UI or from the command line.

bwadmin Command Line

To view the status of the AppNode MyAppNode in the AppSpace MyAppSpace, execute the following command at the command line:

: 

BW_HOME\bin>bwadmin show -domain MyDomain -appspace MyAppSpace appnode MyAppNode

Admin UI

Navigate to the AppNode page and view the Status column.

To view heap memory usage, click on the graph view.

Following fields are available:
Field Description
PID Process ID
Active Threads Number of threads currently active on the AppNode
CPU Usage CPU usage percentage
Memory Usage (MB) Memory used versus allocated memory for a process as an AppNode in MB
Heap-Memory Usage Shows used memory out of total memory.
MaxHeapMemory Maximum heap memory that can be allocated to a JVM in bytes