Monitoring in Nexus Timestamp Server

This article describes monitoring in Nexus Timestamp Server.

The Nexus Timestamp Server monitors several internal objects and states such as memory usage, CPU utilization and thread status. The monitoring is implemented through Java Management Extensions (JMX). This in turn caters for flexibility in the protocols used for monitoring. For example, the tool JConsole, included in the Java JDK, may be used to monitor the Nexus Timestamp Server. Several commercial monitoring products also support JMX.

In load-balanced scenarios, where several servers are used, each instance of the server will have its own monitored objects and counters.

Use JConsole

The JConsole tool is found in <jdk-home>/bin.

To start monitoring, find out the PID of the Nexus Timestamp Server.
Enter the command jconsole <pid>.
Once connected, a window looking like this is shown:
You can monitor a variety of system resource parameters, such as:
1. Memory
  1. HeapMemoryUsage
  2. NonHeapMemoryUsage
2. Operating System
  1. ProcessCPUTime
3. Runtime
  1. StartTime
  2. UpTime
4. Threading
  1. ThreadCount
  2. PeekThreadCount