|
Viewing Issue Advanced Details
[ Jump to Notes ]
|
[ View Simple ]
[ Issue History ]
[ Print ]
|
|
ID |
Category |
Severity |
Reproducibility |
Date Submitted |
Last Update |
|
0000457 |
[Resin] |
minor |
always |
11-18-05 00:00 |
01-27-06 14:35 |
|
|
Reporter |
sergek |
View Status |
public |
|
|
Assigned To |
ferg |
|
Priority |
normal |
Resolution |
fixed |
Platform |
|
|
Status |
closed |
|
OS |
|
|
Projection |
none |
|
OS Version |
|
|
ETA |
none |
Fixed in Version |
3.0.18 |
Product Version |
3.0.14 |
| |
Product Build |
3.0.14 |
|
|
Summary |
0000457: Session.setMaxInactivityInterval does not change JDBC expire_interval |
|
Description |
RSN-506
Our app is configured to timeout sessions after 30 minutes. Once you sign in to our admin system, we call session.setMaxInactivityInterval(7200) for 2 hours.
I was just checking persistent_sessions table, and expire_interval is still only 37 minutes for all my sessions. Once more the sessions that I see on my app server that have been idle for more than an hour (but not timed out according to their memory definition) are deleted from the database, suggesting the user would not support bouncing to another server.
I'm also confused as to how my app would even list that session that has been around for more than 1 hour... shouldn't those sessions be flushed from memory once I persistent them to the database? Is there a flag I need to set to make it behave this way? I realize my conf is using both filestore and JDBC store to persistent sessions... I can change that, but this seems a bit odd to me. |
|
Steps To Reproduce |
|
|
Additional Information |
Windows/Linux Java 1.5 Resin 3.0.14 |
|
|
Attached Files |
|
|
|
Relationships 
