Skip to main content
Woohoo! Qlik Community has won “Best in Class Community” in the 2024 Khoros Kudos awards!
Announcements
Nov. 20th, Qlik Insider - Lakehouses: Driving the Future of Data & AI - PICK A SESSION
cancel
Showing results for 
Search instead for 
Did you mean: 
Rema_04
Contributor II
Contributor II

QDS gets disconnected frequently

The QDS service on the prod server gets disconnected frequently with below error:

A timeout (30000 milliseconds) was reached while waiting for a transaction response from the QlikViewDistributionService service.

 

Can anyone help here

Labels (2)
1 Solution

Accepted Solutions
Ray_Strother
Support
Support

Hello,

1. You can adjust the communication timeout between the QMS and QDS server per below link.
https://community.qlik.com/t5/Official-Support-Articles/QlikView-Management-Service-Log-Error-Error-...

2. How busy is your QDS server , does the issue happen when it's under high usage . (meaning reload) .

3. Confirm there aren't any network delay between the servers (if multinode) .

View solution in original post

4 Replies
Ray_Strother
Support
Support

Hello,

1. You can adjust the communication timeout between the QMS and QDS server per below link.
https://community.qlik.com/t5/Official-Support-Articles/QlikView-Management-Service-Log-Error-Error-...

2. How busy is your QDS server , does the issue happen when it's under high usage . (meaning reload) .

3. Confirm there aren't any network delay between the servers (if multinode) .
Rema_04
Contributor II
Contributor II
Author


Thankyou for your response.Regarding your questions, pfb answers:

2. How busy is your QDS server , does the issue happen when it's under high usage . (meaning reload) ->Yes this issue happens when there is high usage by reloads and is very frequent.The CPU usage is high.

3.Confirm there aren't any network delay between the servers (if multinode) ->No, there is no network delay on the platform

marcus_sommer

In general are the various default-configurations to timeouts and similar settings well chosen to ensure performance and stability. Therefore adjustments to them may make the matter even more worse and should be rather not the first measurement.

Before adjusting the working sets and/or the number of available cores and/or the number of max. possible concurrent tasks and/or changing any timeouts and/or moving the tasks into another order/dependency/time-slot or similar measures it would be useful to monitor the happenings on the server with the various log-files from QlikView and the OS - maybe starting with the governance dashboard. 

Chip_Matejowsky
Support
Support

Hi @Rema_04,

Have you reviewed the QMS log? Can you upload it here?

 

Best Regards

Principal Technical Support Engineer with Qlik Support
Help users find answers! Don't forget to mark a solution that worked for you!