mcp-jvm-diagnostics 0.1.10 → 0.1.12

package/README.md

@@ -31,7 +31,7 @@ It analyzes **offline** artifacts (thread dumps, GC logs, heap histograms) rathe
 - Priority support
 
 <!-- TODO: replace placeholder Stripe Payment Link once STRIPE_SECRET_KEY is configured -->
-**$9.99/month** — [Get Pro License](https://buy.stripe.com/PLACEHOLDER)
+**$9.00/month** — [Get Pro License](https://buy.stripe.com/PLACEHOLDER)
 
 Pro license key activates the `generate_report` MCP tool in mcp-jvm-diagnostics.
 

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.9 — MCP server for JVM diagnostics
+    console.log(`mcp-jvm-diagnostics v0.1.12 — 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.9",
+    version: "0.1.12",
 });
 // --- 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.", {
@@ -349,11 +349,11 @@ server.tool("diagnose_jvm", "Unified JVM diagnosis combining thread dump and GC
     thread_dump: z
         .string()
         .optional()
-        .describe("Thread dump text (from jstack, kill -3, or VisualVM). Capture at the same time as the GC log for accurate cross-correlation."),
+        .describe("Thread dump text (from jstack, kill -3, or VisualVM). Capture during active symptoms for meaningful cross-correlation — a dump from a healthy period will not correlate with GC pressure visible in the log."),
     gc_log: z
         .string()
         .optional()
-        .describe("GC log text (from -Xlog:gc* for Java 9+, or -verbose:gc for Java 8). Capture at the same time as the thread dump for accurate cross-correlation."),
+        .describe("GC log text (from -Xlog:gc* for Java 9+, or -verbose:gc for Java 8). Provide the portion covering the time window when the thread dump was taken — trim the log to the symptom window if it is large. Logs from a different time period produce spurious correlations."),
 }, async ({ thread_dump, gc_log }) => {
     try {
         if (!thread_dump && !gc_log) {

package/build/parsers/gc-log.js

@@ -122,6 +122,7 @@ export function parseGcLog(text) {
                 heapAfterMb: Math.round(parseInt(parallelRegionMatch[3], 10) / 1024),
                 heapTotalMb: Math.round(parseInt(parallelRegionMatch[4], 10) / 1024),
             });
+            continue;
         }
     }
     // Calculate time span

package/build/parsers/jfr-summary.js

@@ -119,6 +119,7 @@ function analyzeJfrEvents(events, totalEvents, totalSize) {
     const threadStart = byName.get("jdk.ThreadStart");
     if (threadStart && threadStart.count > 200) {
         issues.push(`${threadStart.count.toLocaleString()} threads started — possible thread churn. Consider thread pooling.`);
+        recommendations.push("Replace ad-hoc thread creation with a fixed-size thread pool (Executors.newFixedThreadPool) or virtual threads (Java 21+) to eliminate thread creation overhead.");
     }
     // Check for exception events
     const exceptions = byName.get("jdk.JavaExceptionThrow");
@@ -130,6 +131,7 @@ function analyzeJfrEvents(events, totalEvents, totalSize) {
     const classLoad = byName.get("jdk.ClassLoad");
     if (classLoad && classLoad.count > 1000) {
         issues.push(`${classLoad.count.toLocaleString()} class loads — excessive class loading may indicate classloader leak or dynamic proxy overuse.`);
+        recommendations.push("Use `analyze_heap_histo` to check java.lang.Class instance count. If growing, look for frameworks that generate proxies or bytecode at runtime (Hibernate, Spring AOP, reflection-heavy libraries).");
     }
     // Check for file/socket I/O
     const fileRead = byName.get("jdk.FileRead");
@@ -140,7 +142,8 @@ function analyzeJfrEvents(events, totalEvents, totalSize) {
         .filter(Boolean)
         .reduce((sum, e) => sum + e.count, 0);
     if (ioCount > 5000) {
-        issues.push(`High I/O activity: ${ioCount.toLocaleString()} file/socket events. Consider batching or buffering.`);
+        issues.push(`High I/O activity: ${ioCount.toLocaleString()} file/socket events recorded.`);
+        recommendations.push("Profile I/O call sites with async-profiler or VisualVM. Common causes: unbuffered writes, per-record DB queries, missing connection pooling. Consider batching writes and reads.");
     }
     // Check for compilation events
     const compilation = byName.get("jdk.Compilation");

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "mcp-jvm-diagnostics",
-  "version": "0.1.10",
+  "version": "0.1.12",
   "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",