Dan Smith created GEODE-6342:
--------------------------------
Summary: ThreadsMonitor prints many warnings in gateway sender
logs if receiver is not running
Key: GEODE-6342
URL: https://issues.apache.org/jira/browse/GEODE-6342
Project: Geode
Issue Type: Bug
Components: management, wan
Reporter: Dan Smith
The new ThreadsMonitor functionality is printing a lot of warnings if you start
a WAN gateway without starting the receiver.
Steps to reproduce:
1. Start a member with a parallel gateway sender attached to a region. The
sender can have any remote-distributed-system-id, we won't create a receiver.
2. Add data to the region
You will see many warnings like below in the logs
{noformat}
[vm6] [warn 2019/01/30 13:29:47.727 PST <ThreadsMonitor> tid=0x24] Thread <132>
that was executed at <30 Jan 2019 13:24:10 PST> has been stuck for <337.015
seconds> and number of thread monitor iteration <5>
[vm6] Thread Name <Event Processor for GatewaySender_sender-parallel-sender_1>
[vm6] Thread state <TIMED_WAITING>
[vm6] Executor Group <GatewaySenderEventProcessor>
[vm6] Monitored metric <ResourceManagerStats.numThreadsStuck>
[vm6] Thread Stack:
[vm6] java.lang.Thread.sleep(Native Method)
[vm6]
org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.processQueue(AbstractGatewaySenderEventProcessor.java:698)
[vm6]
org.apache.geode.internal.cache.wan.AbstractGatewaySenderEventProcessor.run(AbstractGatewaySenderEventProcessor.java:1086)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
