Dear everyone,
We are facing an issue where user keeps reporting an incident of application freeze/hangs or app is busy for longer period. Thereafter they have to kill the session through task manager.
This is happening randomly, when user is switching from one screen to another or they are opening a screen in new window. OR sometimes user is away for few minutes (session expired) from the desktop and then returning back to work.
After some analysis, we found that its not related to the DB long running queries. When user is idle for sometime, then it is possible that theirs session have got expired. IEE might be trying to bring the user online again by issuing refresh token and get the new authentication details for user.
So, during this process, we observed that there are lots of similar authentication calls between IEE and server keeping it busy for such longer period. This is because the newly obtained authentication details (cookies) are not getting passed in the subsequent calls from IEE to the server. This is resulting in continuous authentication calls between IEE and server. After sometime (35 sec/ 5 minutes/10 Mins), one of the call gets successful and then system resumes to normal work. But chances are that the user might have kill the session by that time.
If user waited for response, then at the end, he/she gets soft exception and message - an item with the same key has already been added.
Do we have faced similar situation and what was the solution implemented. Meanwhile, we have raised the concern with our developers and they are looking into it. But good, if we can get some insight into.
