Xiaojian Zhou created GEODE-7631:
------------------------------------
Summary: It's better to change the stuck to running in
ThreadsMonitor message
Key: GEODE-7631
URL: https://issues.apache.org/jira/browse/GEODE-7631
Project: Geode
Issue Type: Bug
Reporter: Xiaojian Zhou
We found following warning message:
bridgegemfire2_15991/system.log:[warn 2019/12/17 23:53:09.074 PST
<ThreadsMonitor> tid=0x29] Thread <1304> (0x518) that was executed at <17 Dec
2019 23:52:28 PST> has been stuck for <40.628 seconds> and number of thread
monitor iteration <1>
This "stuck" term confused us for a while. And we found actually the thread is
still running normally. It just stay in run mode for too long (the limit to
trigger the warning msg is 30 seconds).
It's better to change the word "stuck" into "running" in order not to confuse
customer.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
