OIE Thread Viewer Plugin

A dashboard plugin for Open Integration Engine (OIE) that provides real-time JVM thread monitoring with channel-aware filtering, deadlock detection, and jstack-compatible thread dump export.

Works in both administrators: the classic Swing Administrator and the OIE Web Administrator each show a Thread Viewer dashboard tab — both talk to the same engine-side servlet.

Features

• Live thread table with state, CPU time, blocked/waited counts, and full stack traces
• Channel-aware thread correlation using OIE's thread naming conventions
• Category classification (Channel Processing, Database Pool, HTTP/Servlet, System/JVM, etc.)
• Deadlock detection via ThreadMXBean.findDeadlockedThreads()
• Filterable by search text, channel, category, and thread state
• jstack-compatible thread dump export (compatible with fastthread.io)
• Data retained after stop for offline browsing and export
• Zero overhead when not monitoring — contention tracking enabled only while active
• Admin-only access via OIE's ExtensionPermission system

Requirements

• OIE 4.6.0+
• The Web Support plugin for the Web Administrator UI
• Java 17+

Building

The public repsy mirror does not yet carry the 4.6.0 engine artifacts. Build the engine (ant in donkey/ then server/) from a sibling checkout, install its jars, then build:

ENGINE_DIR=/path/to/engine ./scripts/install-engine-jars.sh
mvn clean package

(CI installs the same jars from the published OIE distribution tarball instead — see .github/workflows/build.yml.)

The plugin ZIP will be in package/target/thread-viewer-1.0.0.zip.

Releasing

CI builds every push/PR against engine 4.6.0 (.github/workflows/build.yml). To publish a release in the shape the OIE Community Store expects (extension ZIP + .sha256 sidecar on a GitHub Release), bump version in oie.json, then tag:

git tag v1.1.0 && git push origin v1.1.0

The tag drives the Maven version (-Drevision), so the packaged pluginVersion matches oie.json automatically (.github/workflows/release.yml). The build also compiles the web administrator UI (package/webadmin/web/plugin.jsx → web/plugin.js, via the frontend-maven-plugin) and packages it into the ZIP under thread-viewer/webadmin/.

To iterate on just the web UI without a full Maven build:

cd package/webadmin
npm install
npm run build   # compiles web/plugin.jsx to the committed web/plugin.js

web/plugin.js is a build artifact that must be regenerated and committed whenever web/plugin.jsx changes.

Installation

Install using the Extensions manager in the OIE Administrator, or manually extract to the extensions directory. A restart is required after installation.

Usage

1. Open the OIE Administrator and navigate to the Threads dashboard tab
2. Click Start Monitoring to begin capturing thread snapshots
3. Use the filters (search, channel, category, state) to narrow the view
4. Click any thread row to view its full stack trace
5. Click Export Thread Dump to save a jstack-compatible dump file
6. Click Stop Monitoring when done — thread data is retained for browsing

Web Administrator

The same plugin ZIP carries a web UI half (webadmin/ inside the ZIP). On an engine with the OIE Web Administrator connected (engine 4.6.0+ with the Web Support plugin), the web admin discovers it automatically after the engine restart — no separate install. A Thread Viewer tab appears below the dashboard status table with the same features as the Swing panel:

• Start/Stop monitoring, Refresh Now, and jstack-compatible Export Thread Dump
• Search, channel, category, and state filters; sortable columns (CPU descending by default)
• Double-click a thread row for full details and its stack trace
• DEADLOCK DETECTED banner when ThreadMXBean reports a deadlock
• Thread data is retained after Stop for browsing and export

The monitoring session survives tab switches and dashboard selection changes, and the tab resyncs with the engine's monitoring state on load (GET /extensions/threadviewer/active). Without the Web Support plugin (or when only the Swing client is used) the webadmin/ folder is simply ignored and the Swing tab works as before.

Thread Dump Export

The exported file follows the standard jstack output format and is compatible with analysis tools such as fastthread.io. The export includes:

• Thread header with name, ID, daemon status, priority, and CPU time
• java.lang.Thread.State with qualifiers (on object monitor, parking)
• Full stack traces with interleaved lock/monitor info
• Locked ownable synchronizers
• Deadlock section

License

MIT License