This monitor checks the number of XML threads currently being processed. There are 16 worker threads in the Citrix XML Service. A count of 16 or more shows that XML requests are not being processed in a timely manner.
This monitor checks the number of XML threads currently being processed over multiple consecutive samples.
There are 16 worker threads in the Citrix XML Service. A count of 16 shows that XML requests are not being processed in a timely manner, which impacts Web Interface/Store Front requests (logons, list and launch applications) being slow or rejected.
Having consistently 10 or more busy XML threads already indicate that XML broker might not be capable of servicing all request in timely manner. By default alert is generated if there are 10 or more busy XML treads on two consecutive samples (5 minutes interval).
Monitoring interval (default = 300)
The value that defines the warning threshold to be used in the comparison (the default value is set to 10)
The number of event occurrences before monitor state changes will be triggered (the default value is set to 2)
The most common reason for the XML service to become unresponsive is because it is busy waiting for a response from the IMA service. Usually, adding CPU power helps reducing IMA service response times and consequently number of busy XML threads.
To see monitor performance values, open XenApp Server Performance view.
|Alert Auto Resolve