java

Analyze IBM i JVMs for memory usage, GC activity, and thread counts.

3|1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/ajshedivy/ibmi-agent-skills --skill java-ajshedivy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: java
Source: https://github.com/ajshedivy/ibmi-agent-skills/tree/main/skills/java
Command: npx skills add https://github.com/ajshedivy/ibmi-agent-skills --skill java-ajshedivy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

IBM i Java Virtual Machines can run with varying memory usage, garbage collection patterns, and thread profiles; this skill centralizes monitoring to identify bottlenecks, misconfigurations, and at-risk JVMs to keep systems healthy.

Core Features & Use Cases

  • Monitor heap memory usage, GC activity, and thread counts across all active JVMs on IBM i.
  • Audit Java home directories, properties counts, and 32/64-bit mode for capacity planning and compliance.
  • Use cases include detecting memory pressure, optimizing JVM sizing, and auditing Java environments for consistency.

Quick Start

Ask the IBM i system for current JVMs and memory/GC data using the ibmi CLI.

Frequently Asked Questions about java

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I monitor IBM i JVM memory usage and garbage collection activity?

To identify JVMs at risk of memory pressure on IBM i, query the system via the ibmi CLI tools. The skill returns memory metrics, GC stats, and thread counts sufficient for audits and remediation across production or test environments.

How do I audit Java home directories and JVM configurations across IBM i servers?

Audit Java home directories, properties counts, and 32/64-bit mode across active IBM i JVMs by querying the system via the ibmi CLI. This returns configuration data sufficient for capacity planning and compliance auditing.

What JVM metrics are needed for performance tuning and capacity planning on IBM i?

JVM memory metrics, GC stats, thread counts, and Java home paths are needed for performance tuning and capacity planning on IBM i. Querying active JVMs via the ibmi CLI returns these metrics to identify memory pressure and optimize sizing.

Can I check thread counts and memory pressure for multiple production JVMs on IBM i?

Yes, you can check thread counts and memory pressure for multiple production JVMs on IBM i. The skill applies across servers to identify JVMs at risk of memory pressure by analyzing heap memory usage, GC activity, and thread profiles.

Why does my IBM i JVM experience memory pressure and how do I troubleshoot it?

To troubleshoot IBM i JVM memory pressure, analyze heap memory usage, GC activity, and thread counts returned by the ibmi CLI. Identifying JVMs with high memory utilization or excessive GC activity pinpoints bottlenecks and misconfigurations for remediation.