Qlik Community

Ask a Question

Knowledge Base

Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team

Announcements
Join this live chat April 6, 10AM EST - QlikView to Qlik Sense REGISTER

Error: StdServer: Fiber Loop stall detected

Andre_Sostizzo
Digital Support
Digital Support

Error: StdServer: Fiber Loop stall detected


You may notice fiber loop errors appearing in the Windows, QlikView and Qlik Sense logs.

e.g:

StdServer: Fiber loop (10b74b020) stall detected: last fiber loop iteration started 120917 ms ago.

Fiber loop is an entirely normal error to see and is usually just a sign of a busy server. It may not show any symptoms to the end user.
Fiber-loop stalls indicate a problem with a Windows fiber (a kind of thread) that has taken too long to respond. It shows up in the Windows error logs and the user may experience this a client crash as the session has been closed. If the browser is refreshed then a new session is created.

If the peak memory usage is sufficient to drive the server up towards the upper control limit (High Working Set default is 90%), then one can expect to see some level of degraded performance and unusual failures as the in-engine cache will be mostly drained of memory. The required and recurring re-calculations of results will also use a lot of CPU, and this is also likely the path of explanation for the observed stalls.

Environments:

  • QlikView 12.00, 12.10 and 12.20 (November 2017)
  • Qlik Sense 3.x , June 2017, September 2017, November 2017, February 2018 and onwards

 

Cause:


Fiber-loop stalls indicate a problem with a Windows fiber (a kind of thread) that has taken too long to respond.
Generally caused by a busy server that may or may not be oversubscribed (causing peaks in resource usage) and/or by slow network performance particularly when working with large apps stored on network device or share.

Resolution:


It would be more a case of investigating the overall server performance, size of the Apps (if these are very large and stored on a network device) perhaps there are issues with Network speed/performance. 
Any performance issues should be investigated with their local IT team to help reduce the number of fiber loop errors reported.

See What are fiber loop errors in the QlikView server event log? for more details, as well as related content below.
 

Related Content:

Labels (1)
Comments
john_oll
Partner
Partner

One link is no longer working and should be remove from the article.

Sonja_Bauernfeind
Digital Support
Digital Support

@john_oll Thanks for the assist, John!

I modified the link to point at the correct location 🙂 

Version history
Revision #:
5 of 5
Last update:
Thursday
Updated by: