[
https://issues.apache.org/jira/browse/GEODE-7312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bruce J Schuchardt updated GEODE-7312:
--------------------------------------
Description:
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.
[~yossireg]
was: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.
> 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
> Time Spent: 10m
> 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.
> [~yossireg]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
