[
https://issues.apache.org/jira/browse/GEODE-5142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16594189#comment-16594189
]
ASF subversion and git services commented on GEODE-5142:
--------------------------------------------------------
Commit b9511465702bf746c1543a6a5eb2369f22f88fb3 in geode's branch
refs/heads/concourse-staging from [~bschuchardt]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=b951146 ]
GEODE-5142 new Thread Monitoring Mechanism
Fixing some formatting problems in stack trace output and other log
messages. One person noticed the monitor saying it was "expiring"
a thread and thought it was doing something other than print stack
traces.
> new Thread Monitoring Mechanism
> -------------------------------
>
> Key: GEODE-5142
> URL: https://issues.apache.org/jira/browse/GEODE-5142
> Project: Geode
> Issue Type: New Feature
> Components: docs, management
> Reporter: yossi reginiano
> Assignee: Joey McAllister
> Priority: Major
> Labels: pull-request-available
> Time Spent: 6h 20m
> Remaining Estimate: 0h
>
> One of the most severe issues hitting our real time application is thread
> stuck for multiple reasons, such as long lasting locks, deadlocks, threads
> which wait for reply forever in case of packet drop issue etc...
> Such kind of stuck are under Radar of the existing system health check
> methods. In mission critical applications, this will be resulted as an
> immediate outage.
> Here we introduce thread monitoring mechanism, to detect threads which are
> stuck for any reason.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
