Incorrect Load Index Of 9999 Is Shown For The VDA's After Upgrading the Delivery Controller To 7.15 LTSR
book
Article ID: CTX230571
calendar_today
Updated On:
Description
Incorrect Load Index Of 9999 is shown for the VDA's after upgrading the Delivery Controller To 7.15 LTSR even though the Load Evaluator thresholds configured are not hit.
The issue is seen only for VDA's where Anonymous users login.
Resolution
The issue has been addressed in XA/XD 7.15 LTSR CU2 under #LC8771
The new code sends the combined notification only if broker supports "notifyuserlogoncomplete" feature the session is not anonymous, otherwise it sends just the "logoncomplete". Now for anonymous users it should be sending a "logoncomplete" and hence sessions would not stay in "sessionpending" state and will reflect the correct load index.
Problem Cause
For anonymous users the active sessions also reflected as SessionsPending (LogonInProgress) due to which high load index was shown for the VDA even though the Load Evaluator thresholds were not hit.This is because Pending Logons (Load Throttling) also contributes to Load Index.
With the introduction of 'NotifyUserLogonComplete' feature, "logon-complete" and 'user notifications" are combined into a single notification.
This results in "logoncomplete" not sent for anonymous sessions, as the "user notifications" are sent only for domain users, and anonymous session users are local accounts.Hence, anonymous user sessions stayed in 'logoninprogress' state, since Broker didn't get a 'logoncomplete' notification for the active sessions.
Issue/Introduction
Incorrect Load Index Of 9999 Is Shown For The VDA's After Upgrading the Delivery Controller To 7.15 LTSR