[
https://issues.apache.org/jira/browse/GEODE-8761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17312720#comment-17312720
]
ASF subversion and git services commented on GEODE-8761:
--------------------------------------------------------
Commit e1f64269cb34949d942ce87994ec9967236ba1ba in geode's branch
refs/heads/support/1.14 from Darrel Schneider
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=e1f6426 ]
GEODE-8761: detect stuck ServerConnection threads (#6226) (#6236)
* The threadMonitorExecutor is now created in the run() method
which causes the correct thread id to be set on it.
* changed threadMonitorExecutor field from protected to private
(cherry picked from commit 89200dca57a3ab57fd98bd1af438944a9aff5f23)
> Add ServerConnection threads to ThreadMonitoring Service
> --------------------------------------------------------
>
> Key: GEODE-8761
> URL: https://issues.apache.org/jira/browse/GEODE-8761
> Project: Geode
> Issue Type: Improvement
> Components: regions
> Affects Versions: 1.9.2, 1.10.0, 1.11.0, 1.12.0, 1.12.1, 1.13.0, 1.13.1,
> 1.14.0
> Reporter: Anilkumar Gingade
> Assignee: Darrel Schneider
> Priority: Major
> Labels: GeodeOperationAPI, blocks-1.14.0, pull-request-available
> Fix For: 1.14.0, 1.15.0
>
>
> In Geode the Thread Monitoring Service (TMS) monitors threads to see if a
> they are stuck; it logs a thread dump of stuck threads after a configured
> time. This ticket is to add ServerConnection threads to be monitored by TMS.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
