|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 1951 | minor | always | 08-20-07 09:58 | 09-04-07 14:04 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 3.0.23 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 3.1.3 | ||
|
|
|||||
| Summary: | 0001951: Session invalidation not occurring | ||||
| Description: |
(rep by Takahiro Fukuda) Description of the issue: In our application, on rare occasions we can not invalidate the session. That is, the session id and other information stored in the session are still available after the session is invalidated. System environment: The issue above happens in the both distributed (apache and several resin servers) and non distributed (apache and a single resin server) environments. Reproducibility: There is no specific situation that the issue above happens. While the Resin server operates, the issue occurs unexpectedly. Once that problem comes up, the issue continues to occur. After we restart Resin server, the problem cease to happen. Question: We suspect that the issue above is similar to the one described in the following URL. http://bugs.caucho.com/view.php?id=1544 [^] Although, it is different that the problem we encountered this time happens in not only the distributed but also non distributed environment. Will you please tell us the reason why the issue above happens and there is any workaround we can take? |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||