Ticket #938 (closed Defect: fixed)
Observing an automatic HTTP Session timeout
| Reported by: | Malte | Owned by: | jri |
|---|---|---|---|
| Priority: | Major | Milestone: | Release 4.4.1 |
| Component: | DeepaMehta Standard Distribution | Version: | 4.7 |
| Keywords: | Cc: | jri, dgf, JuergeN | |
| Complexity: | 3 | Area: | GUI / Usability |
| Module: | deepamehta-webclient |
Description
After being authenticated and operating in a valid HTTP Session, after some time, maybe half an hour, suddenly i am logged out!
19.02.2016 14:30:59 org.ops4j.pax.web.service.jetty.internal.LateInvalidatingHashSessionManager scavenge WARNUNG: Timing out for 1 session(s) with id 1d9bk5e25prty1ln9hi4j1kuh4
After that, i am logged out and when moving the Topicmap i have no write access anymore, which is annoying. I also never experienced this before.
I am running the DeepaMehtan? 4.4.3 Standard Distribution (Binary Release).
Wasn't there a setting to control the timeout, i doesn't seem so.
Thanks for your support!
Change History
comment:2 Changed 9 years ago by Malte
Related to this i file an issue regarding the "username dialog" which resides in the upper right corner of the webclient and should reflect my sessions state as timely as possible #939.
comment:3 Changed 9 years ago by jri
Since DM 4.4 you can set a session timeout in config.properties. By default it is set to 0 (= no timeout). Possibly you missed that setting when updating to 4.4. When this setting is missing Pax Web's default applies, which is 5 minutes I think.
# Session timeout in minutes. Specify 0 for no timeout. org.ops4j.pax.web.session.timeout=0
See https://trac.deepamehta.de/ticket/448#comment:15
Note that since DM 4.7 (in the course of switching from Pax Web to Felix HTTP) the config setting is renamed:
# Session timeout in minutes. Specify 0 for no timeout. org.apache.felix.http.session.timeout=0
comment:4 Changed 9 years ago by jri
General hint: when updating a DM production instance you should always install the provided config.properties file and transfer your custom settings manually to it.
comment:5 Changed 9 years ago by Malte
- Status changed from new to closed
- Resolution set to fixed
Indeed! The latter was my mistake because i assumed that there were no significant changes in the "config.properties" the in between 4.3 and 4.4.3...
Thanks for the clarification, https://trac.deepamehta.de/ticket/938#comment:3 solved my issue. Over the last hour or so i did not loose any of the data i entered. Merci!
Woah, this is really frustrating when one just wants to do some work ... i will try to track this down .. maybe a Firefox update to 44.0.2 plays a role here.