topic Re: Reason of "Socket closed by client" - NON User triggered in QlikView

Reason of "Socket closed by client" - NON User triggered

Wed, 28 Jan 2015 09:55:53 GMT

Hello!

We have an issue where our client users (all used AJAX) are "kicked out" of qlikview after about 45-60 minuter despite us having set session timeout to 180 minutes (both in IIS and Qlikview).

In the logs it states the session ended because "Socket closed by client" i.e. having clicked the X in the upper right hand corner, but this is not true.

So does anybody have any guidance to where this issue might reside? Network issue? Local client settings of a a driver(JDBC)

Any help/pointers are appreciated

BR,

Erik N

below is the event log info at the time I tried to alter some dimension after about 40 min of inactivity

2015-01-15 03:16:56	2015-01-28 11:11:51	4	700	Information	Document Open: Open document: User noerikn has no access to document Forsaljning.qvw
2015-01-15 03:16:56	2015-01-28 11:11:51	1	300	Error	Server: An exception (T) occured during open of Forsaljning.qvw.
2015-01-15 03:16:56	2015-01-28 11:11:51	2	500	Warning	Document Load: The document D:\QlikView\Applications\Forsaljning.qvw failed to load because of no file access [19].
2015-01-15 03:16:56	2015-01-28 11:11:56	4	700	Information	Ticket created: Ticket (7295B87BF0D956F9A35AEBC5595B8670DF70B020) for NORDSTROMS\erik.nordstrom.
2015-01-15 03:16:56	2015-01-28 11:11:56	4	700	Information	Ticket Lookup: Ticket 7295B87BF0D956F9A35AEBC5595B8670DF70B020 was found.
2015-01-15 03:16:56	2015-01-28 11:11:56	1	300	Error	Server: An exception (T) occured during open of Forsaljning.qvw.
2015-01-15 03:16:56	2015-01-28 11:11:56	2	500	Warning	Document Load: The document D:\QlikView\Applications\Forsaljning.qvw failed to load because of no access [15].

Re: Reason of "Socket closed by client" - NON User triggered

marcus_sommer — Wed, 28 Jan 2015 10:17:03 GMT

There are also timeout-settings within the document-properties in tab server.

- Marcus

Re: Reason of "Socket closed by client" - NON User triggered

Wed, 28 Jan 2015 10:52:07 GMT

Thanks,

the settings on the server have been made on both the server side as well as the document itself.

I can see this working as the log will state something like "session closed due to idle time" and idle time is the same amount we have set.

No I think this has something to do with the client side

Re: Reason of "Socket closed by client" - NON User triggered

marcus_sommer — Wed, 28 Jan 2015 11:04:50 GMT

You have set it within the app and in server-setup by documents and performance? Are there any refreshing/reloading from the app within this time-span?

- Marcus

Re: Reason of "Socket closed by client" - NON User triggered

Wed, 28 Jan 2015 12:50:38 GMT

Reloads/refresh only done at night time (5 am).

All settings have been set within the QMC on both system and document level.

When you say "within the app" is that what you mean (i.e. in the QMC). I have attached the settings made (some language is in Swedish sorry)

Re: Reason of "Socket closed by client" - NON User triggered

marcus_sommer — Wed, 28 Jan 2015 13:07:04 GMT

I meant with "within the app" really the qvw and there the document-properties in tab server.

- Marcus

Re: Reason of "Socket closed by client" - NON User triggered

francoiswiid — Fri, 07 Aug 2015 12:05:39 GMT

Hi Erik, did you find the cause?

Re: Reason of "Socket closed by client" - NON User triggered

qliktime — Thu, 24 Aug 2023 07:01:39 GMT

I'm bumping this thread a few years later.

I've now seen this on QlikSense Windows on a QMC reload task. It is a multi node setup. Could it be a network glitch? Never seen it before

Re: Reason of "Socket closed by client" - NON User triggered

cwolf — Thu, 24 Aug 2023 12:04:07 GMT

On the Server where the QV Web Server is installed, modify:

"c:\Program Files\QlikView\Server\Web Server\QVWebServer.exe.config"

Increase the value for "SocketTimeOutInSeconds":

<add key="SocketTimeOutInSeconds" value="600" />

Restart the service "QlikviewWebserver".

- Christian