Qlikview Server Hangs And Then Is Forced To Restart
We are having an issue where the Qlikview Server hangs and then is forced to restart.
During the 10-15 minutes of hanging, the Server CPUs goes crazy.
Also we get an error message if an application is reloading stating the following:
'Exception=System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond'
The problem lies in one of our QlikView Application. I believe that when a QlikView application passes a certain volume of data, the application does not behave as it should.
Our application’s data structure is made up of multiple tables. (please see below)
I can replicated the above issue when I select dimensions that represent different granularities of data, for example selecting BIR Flag in the Bet Table, Event in the Selection Table,Affiliate Name in the Customer Table and a DateTime dimension.
The application is roughly around 800 million rows. I would greatly appreciate it
if someone could tell me why this happens and what I can do to remedy it.
Re: Qlikview Server Hangs And Then Is Forced To Restart
CPU spike is primarily due to the computation involved in QlikView. 10-15 minutes for the qvw to open in your server really concerns me a lot. You should definitely think about data model and UI optimization by understanding the application usage by the users. This is more of a strategic solution and will take more time.
However from the tactical standpoint, you can try the following things to get rid of the Exception.
1) Reduce the application with limited data based on the time period (or calendar period)
2) Split the fact tables based on the subject area instead of having 800million rows in one or two fact tables (as captured in the data model. Sorry the data model pic is not clear).
3) Break the application into various subject area and chain them using document chaining