Mantis - Resin
|
|||||
Viewing Issue Advanced Details | |||||
|
|||||
ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
3284 | crash | always | 01-19-09 08:28 | 01-19-09 21:32 | |
|
|||||
Reporter: | kishore_kadiri | Platform: | |||
Assigned To: | ferg | OS: | |||
Priority: | normal | OS Version: | |||
Status: | closed | Product Version: | 3.0.21 | ||
Product Build: | Resolution: | fixed | |||
Projection: | none | ||||
ETA: | none | Fixed in Version: | 3.1.0 | ||
|
|||||
Summary: | 0003284: sessions/srun_.db has become very large at one of our customers. | ||||
Description: |
Hi All, We are using Resin 3.0.21 version. Following is our present settings: <session-config> <file-store>WEB-INF/sessions</file-store> <session-timeout>$sessionTimeout</session-timeout> <session-max>$sessionMax</session-max> </session-config> sessions/srun_.db has become very large at one of our customers. 1. Is it know issue in Resin 3.0.21? 2. Can we safely delete srun_.db files? 3. Can you please explain what is the purpose of srun_.db and if you have any good documentaion on the same, please provide the same? It would be great if you can provide your advise/comments on the same at the earliest. Appreciate your help as always, Kishore Kadiri |
||||
Steps To Reproduce: | |||||
Additional Information: | |||||
Relationships | |||||
Attached Files: |
Notes | |||||
|
|||||
|
|
||||
|
|||||
|
|