You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Dick Cavender (Jira)" <ji...@apache.org> on 2019/09/26 18:06:05 UTC
[jira] [Closed] (GEODE-6933) Gateway sender alert-threshold not
working
[ https://issues.apache.org/jira/browse/GEODE-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dick Cavender closed GEODE-6933.
--------------------------------
> Gateway sender alert-threshold not working
> ------------------------------------------
>
> Key: GEODE-6933
> URL: https://issues.apache.org/jira/browse/GEODE-6933
> Project: Geode
> Issue Type: Bug
> Components: wan
> Reporter: Mario Ivanac
> Assignee: Mario Ivanac
> Priority: Major
> Labels: needs-review, pull-request-available
> Fix For: 1.10.0
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> When alert-threshold function is activated in gateway senders (set alert-threshold to non zero value),
> event is never raised, for entries which are in queue longer than alert-threshold value.
>
> Printout from logs:
> Monitor = GatewaySenderMXBeanMonitor descriptor = eventsExceedingAlertThreshold And value = 0
>
> It seams that reporting of events which exceed alert threshold (class AbstractGatewaySenderEventProcessor), is working only if dispatcher is instance of GatewaySenderEventCallbackDispatcher.
> With deeper analysis, I got to conclusion that for GatewaySender - dispatcher is instance of {color:#629755}GatewaySenderEventRemoteDispatcher.{color}
> {color:#ff0000}So this function is only working for {color}{color:#808080}AsyncEventQueue, for which dispatcher is instance of GatewaySenderEventCallbackDispatcher.{color}
>
> {color:#808080}The other problem is that _getEventsExceedingAlertThreshold() method of_ _GatewaySenderMBean is always returning hardcoded value (0)._{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)