mcp-jvm-diagnostics 0.1.12 → 0.1.14

package/build/index.js

@@ -13,7 +13,7 @@ import { parseJfrSummary } from "./parsers/jfr-summary.js";
 import { generateReportFromThreadDump, analyzeThreadDumpMarkdown, } from "./reporting.js";
 // Handle --help
 if (process.argv.includes("--help") || process.argv.includes("-h")) {
-    console.log(`mcp-jvm-diagnostics v0.1.12 — MCP server for JVM diagnostics
+    console.log(`mcp-jvm-diagnostics v0.1.14 — MCP server for JVM diagnostics
 
 Usage:
   mcp-jvm-diagnostics [options]
@@ -33,7 +33,7 @@ Tools provided:
 }
 const server = new McpServer({
     name: "mcp-jvm-diagnostics",
-    version: "0.1.12",
+    version: "0.1.14",
 });
 // --- Tool: analyze_thread_dump ---
 server.tool("analyze_thread_dump", "Parse a JVM thread dump (jstack output) and analyze thread states, detect deadlocks, identify lock contention hotspots, and find thread starvation patterns. Handles both platform threads and virtual threads (Java 21+). Note: deadlock detection covers synchronized monitor locks only — java.util.concurrent.locks.ReentrantLock and other j.u.c lock types do not expose their waiters in thread dump lock info and will not be detected.", {
@@ -211,10 +211,13 @@ server.tool("analyze_heap_histo", "Parse jmap -histo output and detect memory le
 server.tool("compare_heap_histos", "Compare two jmap -histo snapshots taken at different times to detect memory growth patterns, leak candidates, and new allocations. Captures what is growing between snapshots.", {
     before: z
         .string()
-        .describe("The FIRST (earlier) jmap -histo output"),
+        .describe("The FIRST (earlier) jmap -histo output. Capture from a stable baseline — before the suspected leak window or after application startup has settled. " +
+        "Use `jmap -histo:live <pid>` to force a GC before capturing, ensuring unreachable objects are excluded and the snapshot reflects true live objects."),
     after: z
         .string()
-        .describe("The SECOND (later) jmap -histo output"),
+        .describe("The SECOND (later) jmap -histo output. Capture after reproducing the suspected leak or after running under load. " +
+        "Allow at least 5-10 minutes between snapshots — short gaps may not accumulate enough growth to distinguish real leaks from normal allocation churn. " +
+        "Use the same `jmap -histo:live` flag as the before snapshot for a fair comparison."),
 }, async ({ before, after }) => {
     try {
         const report = compareHeapHistos(before, after);

package/build/parsers/jfr-summary.js

@@ -99,10 +99,20 @@ function analyzeJfrEvents(events, totalEvents, totalSize) {
     // Check for excessive allocation events
     const allocTLAB = byName.get("jdk.ObjectAllocationInNewTLAB");
     const allocOutside = byName.get("jdk.ObjectAllocationOutsideTLAB");
-    if (allocOutside && allocOutside.count > 100) {
+    if (allocOutside && allocOutside.count >= 100) {
         issues.push(`${allocOutside.count.toLocaleString()} allocations outside TLAB — objects too large for thread-local allocation buffers.`);
         recommendations.push("Review large object allocations. Consider increasing TLAB size with -XX:TLABSize or reducing object sizes.");
     }
+    else if (allocOutside && allocTLAB && allocOutside.count > 0) {
+        // Even if the absolute count is low, a high ratio of outside-TLAB to total sampled
+        // allocations indicates pervasive large-object pressure in a low-event recording.
+        const totalSampled = allocTLAB.count + allocOutside.count;
+        const outsidePct = allocOutside.count / totalSampled;
+        if (outsidePct > 0.2) {
+            issues.push(`${allocOutside.count.toLocaleString()} allocations outside TLAB (${(outsidePct * 100).toFixed(0)}% of sampled allocations) — large object pressure detected.`);
+            recommendations.push("Review large object allocations. Consider increasing TLAB size with -XX:TLABSize or reducing object sizes.");
+        }
+    }
     // Check for thread contention
     const monitorEnter = byName.get("jdk.JavaMonitorEnter");
     const monitorWait = byName.get("jdk.JavaMonitorWait");

package/build/reporting.js

@@ -6,7 +6,7 @@ import { analyzeContention } from "./analyzers/contention.js";
 import { detectDeadlocks } from "./analyzers/deadlock.js";
 import { parseThreadDump } from "./parsers/thread-dump.js";
 const PRODUCT_NAME = "jvm-diagnostics";
-const TOOL_VERSION = "0.1.7";
+const TOOL_VERSION = "0.1.14";
 export const MISSING_LICENSE_INPUT_ERROR = "Missing required input: license_key";
 export const MISSING_THREAD_DUMP_ERROR = "Missing required input: thread_dump";
 export const MISSING_ENV_LICENSE_ERROR = "MCP_LICENSE_KEY environment variable is not set. generate_report requires a valid Pro license key. Free-tier analysis tools remain available without it.";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mcp-jvm-diagnostics",
-  "version": "0.1.12",
+  "version": "0.1.14",
   "description": "MCP server for JVM diagnostics — analyze thread dumps, detect deadlocks, parse GC logs, and get JVM tuning recommendations",
   "mcpName": "io.github.dmitriusan/mcp-jvm-diagnostics",
   "author": "Dmytro Lisnichenko",