Periodic Logging of Server Status
The Universal Messaging server writes status information to the log file at regular intervals. The default interval can be configured using the StatusBroadcast realm configuration property, and the default value is 5 seconds).
For information on realm configuration properties, see the section
Realm Configuration in the
Enterprise Manager part of the
Administration Guide.
Here is a sample status log message:
ServerStatusLog> Memory=481, Direct=355, Mapped=0, OpenFileDesc=81,
EventMemory=0, Disk=81913, CPU=1.5, Scheduled=51, Queued=0,
Connections=2, BytesIn=3898, BytesOut=194852, Published=0, Consumed=0,
QueueSize=0, ClientsSize=0, CommQueueSize=0
The following table describes the status log metrics:
Metric | Description | Unit |
Memory | Free JVM memory | Megabyte |
Direct | Free direct memory | Megabyte |
Mapped | Used mapped memory | Megabyte |
OpenFileDesc | On Unix only. The number of file descriptors opened by the Universal Messaging server process | |
EventMemory | JVM memory consumed by events | Megabyte |
Disk | Free disk space in UM data directory | Megabyte |
CPU | Recent CPU usage for the JVM process in percent. Valid values are from 0 to 100 percent. | % |
Scheduled | Number of tasks in the internal scheduler | |
Queued | Number of total tasks currently queued in all thread pools | |
Connections | Active Universal Messaging connections | |
BytesIn | Total bytes received for currently active Universal Messaging connections | byte |
BytesOut | Total bytes sent for currently active Universal Messaging connections | byte |
Published | Total number of consumed events | |
Consumed | Total number of published events | |
QueueSize | Cluster queue size (present only if the realm is part of a cluster) | |
ClientsSize | Cluster client request queue size (present only if the realm is part of a cluster) | |
CommQueueSize | Cluster communication queue size (present only if the realm is part of a cluster) | |
During server startup and each time the log file is rolled, a status log legend is printed in the log file:
ServerStatusLog> Activating Realm status log with format:
Memory - free memory (MB)
Direct - free direct memory (MB)
Mapped - Used mapped memory (MB)
OpenFileDesc - File descriptors opened by process (Unix only)
EventMemory - used event memory (MB)
Disk - free disk space (MB) in server data directory
CPU - cpu load average
Scheduled - scheduled tasks
Queued - total queued tasks in all thread pools
Connections - active connections count
BytesIn - total bytes received (for all active connections)
BytesOut - total bytes send (for all active connections)
Published - total count of published events
Consumed - total count of consumed events
QueueSize - cluster queue size
ClientsSize - cluster client request queue size
CommQueueSize - cluster communication queue size
Periodic logging of the server status can be disabled using the EnableStatusLog realm configuration property.
For information on realm configuration properties, see the section
Realm Configuration in the
Enterprise Manager part of the
Administration Guide.
For information on log rolling, see the section
The Enterprise Manager Logs Panel in the
Enterprise Manager part of the
Administration Guide.