StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>The amount of data you provide is a bit overwhelming, so let's just give you a hint how to proceed. For the analysis I use open source <a href="http://java.net/projects/threadlogic/downloads" rel="nofollow noreferrer">threadlogic</a> application based on TDA. It takes few seconds to parse 3 MiB worth of data but in nicely shows 22 different stack trace dumps in one file:</p> <p><img src="https://i.stack.imgur.com/2XjcO.png" alt="Dumps"></p> <p>Drilling down to reveals really disturbing list of warnings and alerts.</p> <p><img src="https://i.stack.imgur.com/FPv59.png" alt="Alerts"></p> <p>I don't have time to examine all of them, but here is a list of those marked as FATAL (keep in mind that false-positives are also to be expected):</p> <blockquote> <h1>Wait for SLSB Beans</h1> <p><em>Description</em>: Waiting for Stateless Session Bean (SLSB) instance from the SLSB Free pool</p> <p><em>Advice</em>: Beans all in use, free pool size size insufficient</p> <h1>DEADLOCK</h1> <p><em>Description</em>: Circular Lock Dependency Detected leading to Deadlock</p> <p><em>Advice</em>: Deadlock detected with circular dependency in locks, blocked threads will not recover without Server Restart. Fix the order of locking and or try to avoid locks or change order of locking at code level, Report with SR for Server/Product Code</p> <h1>Finalizer Thread Blocked</h1> <p><em>Description</em>: Finalizer Thread Blocked</p> <p><em>Advice</em>: Check if the Finalizer Thread is blocked for a lock which can lead to wasted memory waiting to be reclaimed from Finalizer Queue</p> <h1>WLS Unicast Clustering unhealthy</h1> <p><em>Description</em>: Unicast messaging among Cluster members is not healthy</p> <p><em>Advice</em>: Unicast group members are unable to communicate properly, apply latest Unicast related patches and enable Message Ordering or switch to Multicast</p> <h1>WLS Muxer is processing server requests</h1> <p><em>Description</em>: WLS Muxer is handling subsystem requests</p> <p><em>Advice</em>: WLS Server health is unhealthy as some subsystems are overwhelmed with requests which is leading to the Muxer threads directly handling requests. instead of dispatching to relevant subsystems. There is likely a bug here.</p> <h1>Stuck Thread</h1> <p><em>Description</em>: Thread is Stuck, request taking very long time to finish</p> <p><em>Advice</em>: Check why the thread or call is taking very long??. Is it blocked for unavailable or bad resource or contending for Lock?. Can be ignored if it is doing repeat work in a loop. (like adapter threads polling for events in a infinite loop)...</p> </blockquote>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload