Wt

What happens on the client side when this occurs? Does the application stop working, or is a new session started?

What happens is that the multi session cookie has expired on the client side (it is normally refreshed at regular intervals), but the session id is still valid. What is your session timeout interval?

I'll see if there's a way to make sure that there can be no valid session with an expired multi session cookie. Also, I believe that in this case a new session should be started. I'll check to see if that happens. The only risk here is getting into a state where the multi session cookie is discarded for some reason, and you get into an infinite loop of creating new sessions.

When this happens, the loading indicator is displayed and nothing else. the new session is not started.

the session timeout is 600 (10 minutes)

<!-- Session timeout (seconds). When a session remains inactive for this amount of time, it is cleaned up. -->

600

I have also updated the web browser, I am using Chrome Version 61.0.3163.100.

I think I can see why this can occur. I pushed a possible fix to this to GitHub. Can you check it now?

I extended the validity of the multi session cookie so that the session should always expire before the multi session cookie expires.

Hello,

I am still using WT version 3.3.8 (not yet 4.0)

Can I use the patch anyway ?

cheers

Wt 3 is currently still maintained on the wt3 branch. I pushed the fix to both the wt3 and master (Wt 4) branches.

thank you for your help, I will build a new version of WT3 and keep you informed.

Hi, I have updated my WT3 library, but I still have the errors below, I have closed my laptop at 11:30 then opened it at 12:10

[2017-Oct-06 11:30:23.741562] 6752 - [info] "WebRequest: took 1710.02ms"

[2017-Oct-06 11:30:23.749540] 6752 - [info] "WebRequest: took 18.173ms"

[2017-Oct-06 12:10:08.583119] 6752 - [info] "WebRequest: took 2.38483e+006ms"

[2017-Oct-06 12:10:08.607976] 6752 - [info] "WebRequest: took 24.857ms"

[2017-Oct-06 12:10:08.607976] 6752 - [error] "WebController: Valid session id: F9pp1MLonNUN8UCW, but no cookie received (expecting multi session cookie)"

[2017-Oct-06 12:10:08.619183] 6752 - [info] "WebRequest: took 11.207ms"

[2017-Oct-06 12:10:09.978299] 6752 - [error] "WebController: Valid session id: F9pp1MLonNUN8UCW, but no cookie received (expecting multi session cookie)"

[2017-Oct-06 12:10:09.980000] 6752 - [info] "WebRequest: took 1.701ms"

[2017-Oct-06 12:10:18.134716] 6752 - [error] "WebController: Valid session id: F9pp1MLonNUN8UCW, but no cookie received (expecting multi session cookie)"

[2017-Oct-06 12:10:18.146973] 6752 - [info] "WebRequest: took 14.321ms"

[2017-Oct-06 12:10:18.603279] 6752 - [error] "WebController: Valid session id: F9pp1MLonNUN8UCW, but no cookie received (expecting multi session cookie)"

[2017-Oct-06 12:10:18.611283] 6752 - [info] "WebRequest: took 12.004ms"

No, you don't need to enable WebSockets if you don't want to. Are you experiencing the issue both when testing and in production?

Also, although everything should work with the httpd connector and the fastcgi connector, we do generally recommend using the httpd connector, unless you have a specific reason to use FastCGI.

Yes, I am experiencing the issue both when testing and in production,

I think it was not the case few days before I modify my main widget, replacing WTreeView model from WQueryModel to WStandardModel, but I am not sure that the issue is related to this...

One more question: do you have server push enabled? I guess that maybe that could explain why you got this "WebRequest: took 2.38483e+006ms", even though the session should have timed out after 10 minutes of inactivity. I'm guessing that the browser is not closing the connection when it goes into standby.

Where to check if server push is enabled ? I have a parameter in wt_config.xml :

50

Yes, I was expecting the session to be closed...

I have also updated the web browser, may be the old versions of Chrome close the session when the pc goes in standby mode...

I switched back to WQueryModel as a model of WTreeView, I will tell you in about 30 minutes if there is a relation between them...

Hummmm, not related to what I thought.

If the dead session is detected and the user is redirected to a new session login page it will be ok for me, I would like to avoid keeping the user waiting while nothing will happen.

I've been working on making session expiration more proactive, and I noticed that it should check for expired sessions every 5 seconds with FastCGI. Are you still experiencing this problem in a production setting with the previous patch? If so, I'd have to dig a bit deeper to find an explanation for that.

Yes, I have the same behaviour with FastCGI connector.

Even with the patch from commit c7f7d0a? If so, I'm not sure what is the problem there.

It's been a little while since I've heard anything. Is this issue resolved now, or are you still experiencing this problem?

Hello,

my Wt app is not closed, I still have the loading indicator running indefinitely.

best regards,

In that case, if possible, could you provide a longer log file and maybe also a HAR file (see https://redmine.webtoolkit.eu/projects/wt/wiki/Issue_Tracker_Guidelines#How-to-create-a-HAR-file)?

I'm not sure if the source code of your application plays any role, but if you could provide a code sample (you can send it by mail if you don't want to attach it) that could also help.

I'm out of clues as to why this is still affecting you (the issue that I managed to reproduce has been resolved), so any information could be helpful.

Regards,

Roel