Skip to main content
Announcements
NEW: Seamless Public Data Sharing with Qlik's New Anonymous Access Capability: TELL ME MORE!
cancel
Showing results for 
Search instead for 
Did you mean: 
pth21
Partner - Contributor II
Partner - Contributor II

Total Memory exhausted when using enigma.js

Hello,

We are trying to find out if anyone else has experienced similar issues and figured out what is causing them. 

We recently started developing new mashup using enigma.js Occasionally the Engine stops working properly and we get the error "No available Qlik Sense engine was found. Refresh your browser or contact your system administrator"

We have to restart the services several times to get things back to normal. We are also getting the following errors in the logs.

541 20220927T203811.313+0000 ERROR xxxxxxxxxx System.Engine.Engine 234 7741e2dd-3b40-435d-a5d3-0d09a0bf6f8e xxxxxxxxxx\qsadmin Memory: Total memory exhausted. Attempting recovery: allocating 8.79609e+12 MB 9c3890d6-54a2-4c3c-9591-0f61a0cba49d xxxxxxxxxx yyyyyyy 20220927T203811.108+0000 11104 9356 b19846cd-1f56-48bd-bb13-29c0d520f934 fe6df7a2-65f6-4e9d-8904-d4ea151191b3 20220927T202422.000Z 7741e2dd-3b40-435d-a5d3-0d09a0bf6f8e

168 20220930T161421.112+0000 INFO xxxxxxxxxx System.Engine.Engine 111 118e756e-9c8b-472b-9ed9-29fccf28b338 xxxxxxxxxx\qsadmin IncreaseMemoryQuota: Request GenericObject::GetLayout going MT_HIGH 386530ba-34d3-4532-9100-e3f8ae092d07 xxxxxxxxxx yyyy 20220930T161421.112+0000 9896 12216 0f576bc6-dfa5-4336-bb33-da8622888743 bafe04cc-e56e-42e8-9ad3-54fc24902380 20220930T155446.000Z 118e756e-9c8b-472b-9ed9-29fccf28b338


Sequence# Timestamp Level Hostname Logger Thread Id ServiceUser Message ProxySessionId ActiveUserDirectory ActiveUserId EngineTimestamp EngineThread ProcessId SessionId AppId Server Started
880 20220930T202847.709+0000 WARN xxxxxxxxxx System.Engine.Engine 104 9f79925d-69f3-4a63-ad8e-ad25fdf3bc1b xxxxxxxxxx\qsadmin System: when AAALR(21.563636) is greater than 1.000000, we suggest using new row applicator to improve time and mem effeciency. af0a5abd-5f09-4312-8a16-44fb721e7c99 xxxxxxxxxx yyyy 20220930T202847.703+0000 3972 7052 d00fbbd8-6b0c-4072-991a-6a082f5cb18f fe6df7a2-65f6-4e9d-8904-d4ea151191b3 20220930T192750.000Z

Log Name: Application
Source: Engine
Date: 30/09/2022 8:30:14 PM
Event ID: 300
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: xxxxxxxxxx
Description:
The oplock request is denied.
Restart: Server aborted trying to recover by restart. Reason for restart: Internal inconsistency, type F, detected. [184 (null) -1]

Log Name: Application
Source: Engine
Date: 30/09/2022 8:30:14 PM
Event ID: 300
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: xxxxxxxxxx
Description:
The oplock request is denied.
Restart: Server aborted trying to recover by restart. Reason for restart: Internal inconsistency, general exception detected (Simple Request)

Log Name: Application
Source: Engine
Date: 30/09/2022 8:12:48 PM
Event ID: 300
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: xxxxxxxxxx
Description:
The oplock request is denied.
Restart: Server aborted trying to recover by restart. Reason for restart: Internal inconsistency, general exception in UV event loop

Any hint is highly appreciated.

 

 

 

Labels (2)
3 Replies
hakana
Employee
Employee

GetLayout going MT_HIGH

It sounds like the Hypercube is consuming too much memory.
Are you using an object that exists in the App or creating a new one with enigma?

I would verify your data model to see that it doesn't become very large

pth21
Partner - Contributor II
Partner - Contributor II
Author

Hi Hakana,
Thank you for your reply. 
We are using existing objects from the App and our data model is small. What method is best to use to track the size of the objects being pulled through enigma.js?

I appreciate your help,

Polina

pth21
Partner - Contributor II
Partner - Contributor II
Author

This is an update. I have applied the AAARL change from this article

https://community.qlik.com/t5/Official-Support-Articles/AAALR-is-registered-in-the-Qlik-Sense-logs/t...

and now we need to observe for a couple of days to see if this resolves the issue.

Thank you!