JVM$010W - The Current JVM is not monitored by a JVM collector agent
search cancel

JVM$010W - The Current JVM is not monitored by a JVM collector agent

book

Article ID: 447204

calendar_today

Updated On:

Products

SYSVIEW Performance Management

Issue/Introduction

When attempting to monitor a Java Virtual Machine (JVM) in SYSVIEW, the following warning message is displayed:

JVM$010W - Target JVM is running without a SYSVIEW for JVM Data Collector Agent

Additionally, the JVM may appear in the JVMLIST command but will lack detailed performance data, or the status in the ASADMIN screen may not show as ACTIVE.

Cause

This error occurs when the target JVM is not correctly configured to load the SYSVIEW Data Collector Agent, or the agent fails to initialize within the default timeout period. Common causes include:

  • The -agentpath parameter is missing or incorrectly defined in the JVM startup options.
  • The system is under high load, causing the agent initialization to time out before interceptors can be installed.

Resolution

1. Verify and Configure Agent Path

Ensure that the -agentpath parameter is correctly specified in your JVM_OPTIONS or local-override.cfg file. The path must point to the correct bit-version of the agent library for your JVM.

Example Configuration: JVM_OPTIONS=-agentpath:/path/to/sysview/runtime/jvmdata/bin/libgsvoagt4.so=ssid=GSVX

Note: Replace /path/to/sysview/ with your actual runtime directory and GSVX with your SYSVIEW subsystem ID (SSID).

2. Increase Initialization Retries

On busy systems, the agent may require more time to initialize. You can increase the retry count to extend the initialization window (e.g., to 5 minutes).

  • Option A: Update the monzreqretry parameter in the agent configuration.
  • Option B: Set the environment variable GsvoMonitorZReqInstallRetries=150.

3. Verify Active Monitoring

Once the configuration changes are applied, restart the target JVM and verify the status:

  1. Enter the ASADMIN command in SYSVIEW.
  2. Locate the JVMDATA subtask.
  3. Ensure the status is ACTIVE.
  4. Use the JVMLIST command to confirm that the specific JVM job is now being monitored by the agent.

Additional Information

https://techdocs.broadcom.com/us/en/ca-mainframe-software/performance-and-storage/ca-sysview-performance-management/17-0/administrating/data-collection/configure-data-collection/JVM-Data-Collection/configure-the-jvm-data-collector-agent.html 

Powered by Wolken Software