I think the subect says it all.
It locks too soon for my taste.
Can I edit this somewhere?
It’s a little bit short even for my taste, but IIRC there is no way to change it.
Let’s ask @lucag
Hi, the session time out is defined inside the web.xml of the webapp.
There’s usually no reason to change it, and even if you change it it will be restored on next update (it is ditributed by the repo, I think).
If you feel the need to change it, there must be some specific reason.
What is the problem?
1 Like
The problem is that it expires too soon for our daily use.
We need to re-enter credentials too many times a day.
In the end it is a personal “tool” not a public page, so it should be customizable to a user’s liking.
This should not happen as long as websockets are functioning.
They are designed to keep the session alive while the user is logged in.
Look for the websockets using the Chrome debugger.
- activate debugger at the login page before entering WebTop
- go to Network and activate “WS”
- once logged in you should see the WS named “ABCDE…Atmosphere…”, click on it and select Messages
- You should see messages coming and going on the websocket periodically
If this is not happening, something is killing the websockets on your setup.
Looks like WS are running, mybe they stop at some moment in time so the session ends later? Can you try to keep this open during the day to see what happens when session dies?
I guess. This is a 24/7 PC I have at work to manage things.
I will connect later and see. But it did time out while I was here anyway within the day. It was just on another tab.
Happened again. It just popped that session expired and took me to login screen. The window was never closed.
Remember that I have many tabs on my Edge all the time (and some are pinned too, like webtop) and it can lead to tabs “sleeping” …that is a feature of both Edge and Chrome to save memory and CPU cycles. I don’t know if this keeps the session open.
…I need to keep debug open all day, but I somehow doubt it is a personal issue and not a generic one.
Note that this issue DID happen, but way less, in the past (even with NS7) with some updates more “sensitive” to this, than others. Definitely change to the worse, as I have NS for years (with webtop) and this is the first time I think I report this.
OK I need to re-open this.
I don’t know what happened, but I re-logged-in 3-4 times already today, on an open browser.
Session expires like less than an hour?