You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Bruce J Schuchardt (Jira)" <ji...@apache.org> on 2019/10/21 22:35:00 UTC
[jira] [Resolved] (GEODE-7312) modify the ThreadMonitor to print
the stack of a blocking thread
[ https://issues.apache.org/jira/browse/GEODE-7312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bruce J Schuchardt resolved GEODE-7312.
---------------------------------------
Fix Version/s: 1.11.0
Resolution: Fixed
> modify the ThreadMonitor to print the stack of a blocking thread
> ----------------------------------------------------------------
>
> Key: GEODE-7312
> URL: https://issues.apache.org/jira/browse/GEODE-7312
> Project: Geode
> Issue Type: Improvement
> Components: messaging
> Reporter: Bruce J Schuchardt
> Assignee: Bruce J Schuchardt
> Priority: Major
> Labels: low-hanging-fruit, newbie
> Fix For: 1.11.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> Our thread monitor does a good job of telling us about stuck threads. If a thread is stuck trying to synchronize on an object the monitor even tells us the name of that thread. We should enhance this to give us a stack dump of the thread that owns the lock. Sometimes this is a thread that's not monitored by ThreadMonitor so we don't know what it's doing unless someone takes a thread dump of the whole process.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)