Skip to main content
Announcements
Qlik Community Office Hours - Bring your Ideation questions- May 15th, 11 AM ET: REGISTER NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
BuTbka
Creator
Creator

Qlik Sense "Error when committing"

We encountered a problem when the repository service on the central node consumed 90% of the processor resources and, as a result, the system slowed down and hung. This situation is repeated several times, and we found these 2 lines in the logs. These lines appeared right before the problem occurred.

21525	20230417T133024.759+0300	INFO	QS01	System.Repository.Repository.Core.Repository.ProfessionalAccessTypeRepository	207	d0c68dc0-9219-495e-bbc6-815bddec00b7	DOMAIN\srv.qliksense	Database object has newer timestamp than object being modified; pim4: 63817324220493, itms: 63817322458742, ityp: Repository.Domain.Model.LicenseProfessionalAccessType			c0de92f5-b910-f842-c9b8-e1e00697d0dc	d0c68dc0-9219-495e-bbc6-815bddec00b7
21526	20230417T133024.768+0300	ERROR	QS01	System.Repository.Repository.Core.Repository.Common.TransactionUtility	207	306318f3-7b2b-426a-a74c-31ca074d771c	DOMAIN\srv.qliksense	Error when committing		   at Repository.Core.Repository.Common.AbstractModelRepository.CheckConflicts(IRepositoryObject persistedItem, DateTime itemModifiedDate)↵↓   at Repository.Core.Repository.Common.ModelRepository`1.UpdateMany(IEnumerable`1 items, Boolean appendPrivileges, Int64 privilegesFilter)↵↓   at Repository.Core.Repository.Common.ModelRepository`1.Update(T item, Boolean appendPrivileges, Int64 privilegesFilter)↵↓   at Repository.Core.Licensing.AccessTypes.ProfessionalAccessTypeHandler.<>c__DisplayClass15_1.<TryUseExistingAccess>b__7()↵↓   at Repository.Core.Repository.Common.TransactionUtility.RunInTransaction(ITransaction transaction, IEnumerable`1 actions)	c0de92f5-b910-f842-c9b8-e1e00697d0dc	306318f3-7b2b-426a-a74c-31ca074d771c

What can we do to prevent this issue? We use Qlik Sense Feb 2022 SP 13

Labels (1)
1 Solution

Accepted Solutions
Eugene_Sleator
Support
Support

Hi @BuTbka I think at this point you should open a case with Qlik support. As we will need to look through the logs from your installation, and these should not really be posted here as they contain sensitive information. 

If you do not have a support contact;
Open-a-Support-Case-as-a-Guest 

With support contact;
How-to-contact-Qlik-Support 

 

View solution in original post

12 Replies
Eugene_Sleator
Support
Support

Hi @BuTbka  please refer to this article

If that does not resolve the issue. Cab you please attach the Warning and/or Errors NOT just the lines appearing before the problem occurred.

BuTbka
Creator
Creator
Author

Thanks for answer @Eugene_Sleator !

I saw this article, but it says

To avoid this problem, we have introduced an improvement in the latest Qlik Sense releases that avoids potential conflicts. This improvement is present in Qlik Sense February 2021 Patch 6 and in Qlik Sense May 2021 SR1 or higher releases. An upgrade is recommended to ultimately fix the problem.

We use higher version - Qlik Sense Feb 2022 SP 13

Filtered by error and warn log in attach 

Albert_Candelario

Hello @BuTbka,

Did you investigate why the node consumes so much resources, CPU, is it happening randomly or there is a pattern?

Is the error showed on the log a consequence of the high usage and then we need to tackle the resource issue and not focus on the error per se?

Cheers,

Albert

Please, remember to mark the thread as solved once getting the correct answer
BuTbka
Creator
Creator
Author

Hello @Albert_Candelario,

Qlik Sense Repository Service starts consuming CPU resources as soon as this error appears in the log. This usually happens on a Monday morning, when there is the largest flow of users. In the proxy logs by sessionid, from the error in the repository log, it can be seen that the user opens 2 sessions within a few seconds

Spoiler
21344	14.19.4.0	20230417T133010.663+0300	QS01	401830fa-82d8-41a9-8642-9ec90d3fbb72	Command=Open connection;Result=0;ResultText=Success	c0de9a25-2d20-da7f-dfc7-5d1dd0bbf616	b63e5ccc-141d-4ce6-9cce-440cc8f73572	0	DOMAIN	alex	306279a3-6022-4f88-a091-cb9b62068c0b	Not available	Proxy	AppAccess	/app/306279a3-6022-4f88-a091-cb9b62068c0b?reloaduri=https%3a%2f%2fsense.domain.com%2fsense%2fapp%2f306279a3-6022-4f88-a091-cb9b62068c0b%2fsheet%2f96b9ac4e-4f32-4157-8d30-05fd57300113%2fstate%2fanalysis%3fqlikticket%3duwq2xqw8sdhdybkv	Open connection	0	Backend web socket connection Opened for session 'c0de9a25-2d20-da7f-dfc7-5d1dd0bbf616'. App id: '306279a3-6022-4f88-a091-cb9b62068c0b'. UserAgent: 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/111.0.0.0 Safari/537.36'	401830fa-82d8-41a9-8642-9ec90d3fbb72
21346	14.19.4.0	20230417T133010.832+0300	QS01	8c7c6a04-f7dd-46d9-bf05-528af650f5e2	Command=Start session;Result=0;ResultText=Success	c0de92f5-b910-f842-c9b8-e1e00697d0dc	0	0	DOMAIN	alex	0	DOMAIN\alex	Proxy	Not available	/qps/sessionstart/alex	Start session	0	Start session for user: 'DOMAIN\alex'	8c7c6a04-f7dd-46d9-bf05-528af650f5e2
21431	14.19.4.0	20230417T133045.933+0300	QS01	49d6fc4b-ab44-4413-9cb4-bbd8a7940fc9	Command=Close connection;Result=0;ResultText=Success	c0de9a25-2d20-da7f-dfc7-5d1dd0bbf616	b63e5ccc-141d-4ce6-9cce-440cc8f73572	0	DOMAIN	alex	306279a3-6022-4f88-a091-cb9b62068c0b	Not available	Proxy	AppAccess	/app/306279a3-6022-4f88-a091-cb9b62068c0b?reloaduri=https%3a%2f%2fsense.domain.com%2fsense%2fapp%2f306279a3-6022-4f88-a091-cb9b62068c0b%2fsheet%2f96b9ac4e-4f32-4157-8d30-05fd57300113%2fstate%2fanalysis%3fqlikticket%3duwq2xqw8sdhdybkv	Close connection	0	Backend web socket connection Closed for session 'c0de9a25-2d20-da7f-dfc7-5d1dd0bbf616'. App id: '306279a3-6022-4f88-a091-cb9b62068c0b'. UserAgent: 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/111.0.0.0 Safari/537.36'	49d6fc4b-ab44-4413-9cb4-bbd8a7940fc9
21503	14.19.4.0	20230417T133126.215+0300	QS01	2afcff12-1890-482d-9131-6e042eeba7e3	Command=Open connection;Result=0;ResultText=Success	c0de92f5-b910-f842-c9b8-e1e00697d0dc	1a258f0f-72ef-4720-9af0-f6f2ed91d467	0	DOMAIN	alex	05704077-2e41-4f72-b061-5118b320e22f	Not available	Proxy	AppAccess	/app/05704077-2e41-4f72-b061-5118b320e22f?reloaduri=http%3a%2f%2fsense.domain.com%2fsense%2fapp%2f05704077-2e41-4f72-b061-5118b320e22f%2fsheet%2f9017fa57-9aaf-4606-ad62-c8a86d92061b%2fstate%2fanalysis%3fqlikticket%3dymanp0jypl1-0qth	Open connection	0	Backend web socket connection Opened for session 'c0de92f5-b910-f842-c9b8-e1e00697d0dc'. App id: '05704077-2e41-4f72-b061-5118b320e22f'. UserAgent: 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/111.0.0.0 Safari/537.36'	2afcff12-1890-482d-9131-6e042eeba7e3
23970	14.19.4.0	20230417T134605.633+0300	QS01	c62afce7-9bf0-419c-a64b-e7c6e0a6c1e6	Command=Close connection;Result=0;ResultText=Success	c0de92f5-b910-f842-c9b8-e1e00697d0dc	1a258f0f-72ef-4720-9af0-f6f2ed91d467	0	DOMAIN	alex	05704077-2e41-4f72-b061-5118b320e22f	Not available	Proxy	AppAccess	/app/05704077-2e41-4f72-b061-5118b320e22f?reloaduri=http%3a%2f%2fsense.domain.com%2fsense%2fapp%2f05704077-2e41-4f72-b061-5118b320e22f%2fsheet%2f9017fa57-9aaf-4606-ad62-c8a86d92061b%2fstate%2fanalysis%3fqlikticket%3dymanp0jypl1-0qth	Close connection	0	Backend web socket connection Closed for session 'c0de92f5-b910-f842-c9b8-e1e00697d0dc'. App id: '05704077-2e41-4f72-b061-5118b320e22f'. UserAgent: 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/111.0.0.0 Safari/537.36'	c62afce7-9bf0-419c-a64b-e7c6e0a6c1e6
Eugene_Sleator
Support
Support

Hi @BuTbka yes I read the article am aware of what it says. But I would still try to restart the node as suggested. 

BuTbka
Creator
Creator
Author

Hi @Eugene_Sleator,
Yes, we do. We switch the central node and restart the server. But in some cases, the problem occurs after a few minutes on the second central node, which became active.

Eugene_Sleator
Support
Support

Hi @BuTbka I think at this point you should open a case with Qlik support. As we will need to look through the logs from your installation, and these should not really be posted here as they contain sensitive information. 

If you do not have a support contact;
Open-a-Support-Case-as-a-Guest 

With support contact;
How-to-contact-Qlik-Support 

 

gandalfgray
Specialist II
Specialist II

Hi @BuTbka - We experienced the same issue after a minor upgrade. Did you get a resolution?

BuTbka
Creator
Creator
Author

Hi @gandalfgray no, we still have this issue on August 2023 SP1. And you?