JVM, logs, and time-based diagnosis | WebSphere Administration

Concept and mechanism

WSVR0605W indicates a thread with prolonged activity relative to the configured threshold; it does not prove deadlock. Successive captures help distinguish slow progress from no progress. Correlate stacks with per-thread CPU, dependencies, and the time window. In J9 javacores, an isolated state such as R is not a CPU measurement. Establish the actual JVM and its diagnostic format before applying a recipe. For GC, relate pauses, post-collection occupancy, traffic, and latency. One isolated peak does not establish a memory leak. OutOfMemoryError can also result from native memory, resource limits, or a particular allocation; indiscriminately increasing Xmx can remove native-memory headroom.

Guided application

In a fictional incident after increasing concurrency, preserve the first failure message, javacore, and other available artifacts while respecting sensitivity and space. The collection plan should specify process, interval, volume, and owner. Log paths depend on profile and configuration; do not assume verbose GC always resides in one fixed file. SystemOut, SystemErr, native logs, and HPEL when enabled have different reading methods. Broad tracing can cause overhead and fill the filesystem: restrict components, duration, and rotation while preserving the useful window. Transaction logs support recovery and should not be treated as disposable trace. Mitigation can restore service before the cause is established, but the record should distinguish those two stages.

IN PRACTICE

Free heap with OOM and many threads suggests investigating native consumption and limits before increasing Xmx.

Common pitfalls

Threshold as deadlock; R state as CPU; every OOM as heap; permanent unbounded trace.

Related topics: ND topology and effective configuration · Deployment, routing, and state · JDBC, pools, and transaction outcomes

Take this idea with you

Correlate time-based evidence and account for collection cost.

Create account

Reference: J9 javacore and memory diagnosis · DR WebSphere traditional ND 9.0.5; maintenance baseline 9.0.5.29 (2026-09-08); documentation reviewed 2026-09-30