geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mario Ivanac (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (GEODE-6933) Gateway sender alert-threshold not working
Date Mon, 08 Jul 2019 07:59:00 GMT

     [ https://issues.apache.org/jira/browse/GEODE-6933?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Mario Ivanac updated GEODE-6933:
--------------------------------
    Description: 
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}

  was:
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}{color:#FF0000}AsyncEventQueue,
for which dispatcher is instance of GatewaySenderEventCallbackDispatcher.{color}
{color}


> 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
>
> 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
(v7.6.3#76005)

Mime
View raw message