Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
mubinoddin
Contributor II
Contributor II

Server going to Soft Hang state

Hello Qlik Community

In our organization, the server in which Qlikview is installed frequently goes into soft hang state at the time when no applications are reloading in QMC and no qlikview files are open and basically not much activity is going on in the server. The CPU and memory consumption is also at the minimum at that time. What could be the possible reason ? If there is any actionable from Qlikview side, please let me know.

Labels (1)
1 Solution

Accepted Solutions
marcus_sommer

It's not the default behaviour of QlikView. It might be an effect of customizing the various timeout- and/or CPU/RAM threshold-settings within the QMC and/or directly within the settings-files. If there were changes there is hopefully also a documentation when/what/where/why these changes were applied and also that appropriate backup's exists to restore the default state again.

If there were no such essential changes on the QlikView settings it could be that the environment in which QlikView runs is responsible for this behaviour. For example a VM host which doesn't respect the hardware-reservation of a tool and/or the OS and just distributes it anywhere and/or the OS/VM/BIOS forced any energy-savings from which QlikView didn't awake again. Any touch from the outside of the QlikView services is quite risky that anything will hang.

- Marcus

View solution in original post

1 Reply
marcus_sommer

It's not the default behaviour of QlikView. It might be an effect of customizing the various timeout- and/or CPU/RAM threshold-settings within the QMC and/or directly within the settings-files. If there were changes there is hopefully also a documentation when/what/where/why these changes were applied and also that appropriate backup's exists to restore the default state again.

If there were no such essential changes on the QlikView settings it could be that the environment in which QlikView runs is responsible for this behaviour. For example a VM host which doesn't respect the hardware-reservation of a tool and/or the OS and just distributes it anywhere and/or the OS/VM/BIOS forced any energy-savings from which QlikView didn't awake again. Any touch from the outside of the QlikView services is quite risky that anything will hang.

- Marcus