Home
  •  

Incoming Messages Timed out

Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.AccessEdge.PERF_THROTTLE_MESSAGES_HELD_ABOVE_TIMEOUT (UnitMonitor)

Knowledge Base article:

Summary

The number of incoming messages currently being held by the server for processing for more than the maximum tracking interval.

Causes

This server is too busy and is unable to process user requests in timely fashion.

Resolutions

This might be a temporary condition. If the problem persists, please ensure that hardware and software requirements for this server meet the user usage characteristics.

Element properties:

TargetMicrosoft.LS.2013.Component.AccessEdge
Parent MonitorSystem.Health.PerformanceState
CategoryPerformanceHealth
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeMicrosoft.LS.2013.Performance.Double.ConsecutiveThresholdMonitor
RemotableTrue
AccessibilityPublic
Alert Message
[LYNC] The number of incoming messages currently being held by the server for processing for more than the maximum tracking interval.
Perf Object Name:
Perf Counter Name: SIP - Incoming Messages Timed out
Perf Counter Value: {0}
Error Threshold: 250
Warning Threshold: 200
Consecutive Samples Repeat Count: 1

Please see the 'Product Knowledge' and the 'Alert Context' tab on Alert Properties view for more information.
RunAsDefault

Source Code:

<UnitMonitor ID="Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.AccessEdge.PERF_THROTTLE_MESSAGES_HELD_ABOVE_TIMEOUT" Accessibility="Public" Enabled="true" Target="Microsoft.LS.2013.Component.AccessEdge" ParentMonitorID="Health!System.Health.PerformanceState" Remotable="true" Priority="Normal" TypeID="Microsoft.LS.2013.Performance.Double.ConsecutiveThresholdMonitor" ConfirmDelivery="false">

  <Category>PerformanceHealth</Category>

  <AlertSettings AlertMessage="Alert_The_number_of_incoming_messages_currently_being_held_by_the_server_for_processing_for_more_than_the_maximum_tracking_interval.">

    <AlertOnState>Error</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>Error</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Data/Context/SampleValue$</AlertParameter1>

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

    <OperationalState ID="Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.AccessEdge.PERF_THROTTLE_MESSAGES_HELD_ABOVE_TIMEOUT_OverThreshold" MonitorTypeStateID="OverThreshold" HealthState="Error"/>

    <OperationalState ID="Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.AccessEdge.PERF_THROTTLE_MESSAGES_HELD_ABOVE_TIMEOUT_UnderThreshold" MonitorTypeStateID="UnderThreshold" HealthState="Success"/>

    <OperationalState ID="Microsoft.LS.2013.Monitoring.UnitMonitor.ThresholdPC.AccessEdge.PERF_THROTTLE_MESSAGES_HELD_ABOVE_TIMEOUT_UnderThresholdOverThreshold" MonitorTypeStateID="UnderThresholdOverThreshold" HealthState="Warning"/>

  </OperationalStates>

  <Configuration>

    <ComputerName>$Target/Host/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>

    <CounterName>SIP - Incoming Messages Timed out</CounterName>

    <ObjectName>LS:SIP - Load Management</ObjectName>

    <InstanceName/>

    <AllInstances>false</AllInstances>

    <Frequency>900</Frequency>

    <WarningThreshold>200</WarningThreshold>

    <ErrorThreshold>250</ErrorThreshold>

    <NumSamples>1</NumSamples>

  </Configuration>

</UnitMonitor>