Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsWebLogic calls a thread “stuck” when it has remained continuously busy longer than the configured maximum time. That status is a signal to investigate—not a diagnosis of what is blocking the request. To detect one, inspect the affected server’s thread monitoring page, then capture and compare thread dumps to find the work that is taking too long.
How does WebLogic detect a stuck thread?
WebLogic Server classifies a thread as stuck when it is continually working, rather than idle, for longer than the configured Stuck Thread Max Time. The Stuck Thread Timer Interval controls how often the server scans for threads that have exceeded that limit. These are separate settings: the maximum time is the busy-duration threshold, while the interval is the scan frequency. See Oracle’s Tuning stuck thread detection behavior.
For WebLogic Server 14.1.1, Oracle’s MBean reference lists a default StuckThreadMaxTime of 600 seconds. An administrator can configure a different value; do not assume the default applies to another release or to a server whose setting has been changed.
A stuck status does not identify the cause. A long-running request may be waiting on a dependency, blocked in application code, or doing legitimately lengthy work. The thread count alone cannot distinguish these possibilities.
#1 Best Overall
How do I detect a stuck thread in Oracle WebLogic?
- Confirm the release and current settings. In the Administration Console for WebLogic Server 14.1.1, go to Environment > Servers, select the affected server, then open Configuration > Tuning. Review Stuck Thread Max Time and Stuck Thread Timer Interval. Oracle says to save and activate changed detection values, then reboot the server for them to take effect. Check the matching documentation for other releases.
- Inspect the thread pool. Open Monitoring > Threads for the affected server. Compare stuck and hogging counts with idle and active threads, queue length, and throughput. For individual threads, note the current request, transaction, Work Manager, application, and module, as well as whether the thread is marked idle or stuck.
- Capture thread stacks. On the selected server, open Monitoring > Performance and choose Dump Thread Stacks. If the condition persists or recurs, take multiple dumps at evenly spaced intervals so you can compare what the threads are doing over time.
- Check server health and queue scope. Establish whether the problem affects one thread, an application’s work, or an entire execute queue. Correlate health changes with queue length, incoming and completed requests, and the user-facing impact.
Oracle’s WebLogic Server tuning guidance notes that a stuck thread cannot complete its current work or accept new work, and that the server logs a message each time it diagnoses one. The Administration Console’s thread-monitoring fields help put that message in context; they do not by themselves explain why the work is slow.
What is the difference between a stuck thread and a hogging thread?
A stuck thread has exceeded the configured busy-time threshold. A hogging thread is being held by a request much longer than normal, as observed by the scheduler, but may return before the stuck threshold is reached. A hogging count can therefore be an early warning, not proof that the stuck-thread limit has been crossed. Use the individual thread’s status and the configured threshold to interpret the two counts.
Rank #2
How do I troubleshoot WebLogic stuck threads?
Compare repeated thread dumps
One dump shows where a thread is at a single moment; several evenly spaced dumps can show whether it remains in the same method or progresses. Look for common methods or call paths among affected threads, and check whether they point to the same application component or dependency. Oracle’s troubleshooting guidance recommends thread dumps for investigating deadlocks and repeated dumps to identify methods taking a long time.
Relate thread activity to the queue and impact
Use the thread page’s request, Work Manager, application, and module details to group affected work. Compare that context with queue length and throughput: a rising queue with low completion activity signals a different operational problem from a small number of long requests while the rest of the pool remains available. Treat these fields as clues for narrowing the investigation, not as proof of a root cause.
Adjust detection thresholds only when justified
Do not lower the maximum time reflexively to make the server report stuck threads sooner. First determine whether legitimate requests normally exceed the current limit; an overly short threshold can classify expected work as stuck. Consider both the configured maximum time and scan interval, then apply changes using the documented save, activate, and reboot process for the deployed release.
What happens when an execute queue is fully stuck?
Oracle documents warning and critical health states when all threads in an execute queue are stuck. Check how broad the condition is and correlate the health transition with queue length, request arrivals and completions, and application impact. A health alert identifies severity, but does not reveal what is keeping the work from completing.
Rank #4
Should I configure automatic recovery with Work Manager triggers?
Work Manager triggers can respond to stuck-thread conditions, but their actions affect availability and should follow an understanding of the workload and recovery goal. Depending on the configured trigger, WebLogic can shut down the Work Manager, move the application into admin mode, or mark the server failed. Oracle documents trigger controls based on stuck-thread count and maximum stuck time, including behavior that can resume a Work Manager after threads clear. Confirm the exact behavior and scope in the documentation for your deployed version before enabling an action; automation is not a substitute for finding why the work is blocked.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Which WebLogic version do these steps apply to?
The console paths and tuning behavior described here are documented for WebLogic Server 14.1.1. The 600-second default is also from the 14.1.1 MBean reference, not a universal value. Work Manager API material may describe a different release; for example, the relevant API documentation is from the 12.1.3 API set. Verify console labels, configuration behavior, and trigger semantics against the documentation matching your installed release before changing production settings.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
