[
https://issues.apache.org/jira/browse/GEODE-7312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16957398#comment-16957398
]
ASF subversion and git services commented on GEODE-7312:
--------------------------------------------------------
Commit 59459c218ce9eb78f527e651867aa6f260eb15ac in geode's branch
refs/heads/feature/GEODE-7258 from Bruce Schuchardt
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=59459c2 ]
GEODE-7312: modify the ThreadMonitor to print the stack of a blocking thread
Log a thread trace for a thread that's blocking a "stuck" thread.
This will help a lot when a user experiences hung operations. Prior to
this change we needed to request thread dumps for servers and that was
usually not possible to obtain because the servers had already been
terminated & restarted. This change puts the relevant thread dumps in
the server's log file, which is much easier for folks to gather after
the fact.
> 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)
