From time to time we got an “Invalid Session” dialog from our Wisej WebApplication, if we left for several minutes the browser tab.
It took some time, but I think now we found the reason for that.
In our application we set the SessionTimeout in default.json to 8h.
IIS-Settings are set to default. So, SessionTimeout and ApplicationPool timeout are set to 20min.
I was looking for some KeepAliveSignal/HeartbeatSignal in defalut.json documentation, but without success.
Looking at the Wisej-Sources I finally found something. It is called keepAliveInterval and you can set it also in default.json.
But per default it is calculated in dependence of the SessionTimeout, which is set in default.json. So, in our case we have a SessionTimeout of 8h, which means that keepAliveInterval is set by Wisej to 2h. As a result of this, if no one interacts with the application for 20min, the application pool was cleaned up and we got the “Invalid Session” message box.
Possible solutions are now:
We could only reproduce this behavior, when setting “enableWebSocket”: false in default.json.
Could it be, because of the duplex WebSocket connection the KeepAlive is send on a different way?
Please login first to submit.