| [#163] | project: bugtracking | priority: high | category: bug | |
|---|---|---|---|---|
| submitter | assigned to | status | date submitted | |
| Philippe | Burak | fixed | 2003-09-30 13:17:09.0 | |
| subject | bugtracking sessions time out | |||
| code | ||||
| what happened | After some time, the scala bugtracking session are no more valid and a new login is required. |
|||
| what expected | The sessions should be valid forever. | |||
| [back to overview] | ||||
| Burak edited on 2003-10-01 17:35:43.0 |
|
I hope I did it now.
Again, the documentation in the config files of the server misguided me... don't believe in comments... never... |
| Burak edited on 2003-10-03 18:52:27.0 |
| hm, no did not seem to work. |
| Philippe edited on 2003-10-07 11:29:25.0 |
|
Changed priority to high. |
| Burak edited on 2004-04-15 16:51:12.0 |
|
should be fixed, using HttpSession::setMaxInactiveInterval(-1).
There are 3 locations where timeouts can be adjusted. Calling HttpSession::setMax... seems to override all. |