Apache OpenOffice (AOO) Bugzilla – Issue 3420
Increase session timeout to 8 hours
Last modified: 2003-12-27 10:23:17 UTC
It happens quite often that I enter a bug report and need a bit longer to collect all information, copy source examples and describe the steps to reproduce the bug. Sometimes a phone call interrupts me etc. It also takes quite some time to follow proposed solutions, workarounds and so on until I finally add a new comment. Then, when I'm finished, Issuezilla rejects my report or comment and claims I'm not logged on. My report is of course lost, when this happens. I already started the habit to copy every report to the clipboard before sending it, that's how bad it is. Proposal: can we increase the session timeout to two hours (to be sure) or at least to an hour? I don't see how this could hurt anyone.
I suspect this is an issue for product management of IZ but I will send it to support here to see if they have a quick fix. reassigning. louis
Hi, I think this may be a version of IZ 2148, which is to allow "seamless logging back ..." when updating issues. That fix will be implemented in SourceCast 1.3, which won't be due until sometime later this year. louis
It's similar to #2148, but not the same. This issue asks that a session should be valid longer than the current timeout time. (#2148 asks for seemless login after being logged out or never logged in).
The session timeout is the same all over OpenOffice.org, as far as I know. NetBeans has requested that their timeout be increased, but OpenOffice has never requested this (until now). We can increase it, but this will be a P3 TASK and may take some time (it needs to be done by hand by an instantiations engineer). Is this okay with you, Stefan?
Yes! Do you know the current timeout value? Netbeans used 8 hours. If this wouldn't stress our resources too much, I would like to use it for OOo also.
Yes, I believe 8 hours would be okay. I've submitted the request to our instiations group (PCN9584).
This was included in the inst of the current rollout and brought live.
As agreed by Louis I will close these resolved fixed support-owned issues now. If you have trouble with that, please re-open the issue.