Wt

It may be related to a DoS fix that we fixed in 3.3.6, but I am not sure how normal behavior can trigger this: what may be relevant is the events that you are listening to, whether you use server push, websockets, ...?

Hey Koen

It's really weird. It's like just after so much time it starts happening. Nothing like sessions getting destroyed. I am using server push / long polling. No websockets. We have a few things that are happening in separate threads, but they are posting their changes via WServer::post(). The only event on the application that we are really listening for is internalPathChanged. If there is more I can do to help figure out this issue please let me know. We would like to push 3.3.6 as soon as we figure out this bug!

Thanks so much for your help.

We are tyring to reproduce the issue here, so anything other information that could help is welcome, for example how frequently are server push updates happening?

Also, a pastebin of my current wt_config.xml file can be found here: http://pastebin.com/CejfXJFY

Thanks Again!

It seems that the issue starts when the session sits idle for a little bit but doesn't expire. In the browser you get the "working" cursor and nothing happens until you refresh the page. No events will process until a full page refresh. It seems that it happens after a few server push keep alive requests. If I can send anything else, please let me know! Thanks!

Can you send me a log file? You may send it to my email address, if you prefer (koen@emweb.be).

Hey Koen

Please find the log files attached. It happens after the session sits idle and a couple of server keep alives happen. In the logging parameters I am using "* debug:wthttp". Please let me know what else I can provide.

Thanks!

Thanks, we could reproduce the problem. The issue will appear when server push is enabled, without WebSockets, and sitting idle for over about 2 minutes. The latest wt git version should fix this, can you confirm?

Koen

Thanks for the follow-up! I'll pull the latest git repo and build and see if it fixes the problem. I'll update after I can confirm.

Koen!

Thank you for the help! Works very well according to my first tests. I will post here again if I run into any issues! Thanks again!

As a side note did anything change with the refresh() methods? It seems that some of mine aren't getting called that used to when I override them in my subclasses?

Hi Koen!

Looks like I have the same issue while my jwt library is the latest one (includes "fix two vulnerabilities" change)

Still just after 1) enableUpdates( true ); in app constructor 2) several widget tree operations w/o push 3) 2-minute idle time session -

I see WARN eu.webtoolkit.jwt.WebSession - secure:invalid ackId in the log.

After that any visual operation results in endless "Loading..." indicator.

I can sort out this only by either clicking smth or by pushing smth to the browser.

If you wish you can find sources at http://usvn.ahuman.org/svn/urmweb/.

Hey,

Indeed, I believe this fix isn't in the JWt git repository. We will update it ASAP.

Koen

The latest github version is now in sync with the C Wt version.

Confirmed, thank you!

I am seeing this on one of my Wt4 servers:

INFO: Opened log file (/dev/null).
[2019-Oct-08 22:01:29.335] 2000 [/staff QJZ6zmIwElHm468K] [notice] "login ip:71.78.215.238 w:1920 h:1080 user:Lauren M[13]"
[2019-Oct-08 22:01:29.610] 2000 [/staff QJZ6zmIwElHm468K] [warning] "WApplication: WApplication::addMetaHeader() with no effect"
[2019-Oct-08 22:02:41.726] 2000 [/staff QJZ6zmIwElHm468K] [error] "Wt: decodeSignal(): signal 'odvlznk.render' not exposed"
[2019-Oct-08 22:02:48.327] 2000 - [error] "WebController: could not parse request: Oversized application/x-www-form-urlencoded (58932247)"
[2019-Oct-08 22:02:52.050] 2000 [/staff QJZ6zmIwElHm468K] [error] "Wt: decodeSignal(): signal 'odvlznk.render' not exposed"
[2019-Oct-08 22:02:58.457] 2000 - [error] "WebController: could not parse request: Oversized application/x-www-form-urlencoded (58932253)"
[2019-Oct-08 22:03:08.544] 2000 [/staff QJZ6zmIwElHm468K] [secure] "Wt: invalid ackId"
[2019-Oct-08 22:03:35.855] 2000 [/staff QJZ6zmIwElHm468K] [secure] "Wt: invalid ackId"
[2019-Oct-08 22:04:50.080] 2000 [/staff QJZ6zmIwElHm468K] [secure] "Wt: invalid ackId"
[2019-Oct-08 22:06:50.102] 2000 [/staff QJZ6zmIwElHm468K] [secure] "Wt: invalid ackId"

I think that the "Oversized application/x-www-form-urlencoded" suggests what is really your issue there: the browser is sending requests that are too large, and they're being rejected.

Thank you.