|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 314 | minor | always | 07-14-05 00:00 | 04-05-06 11:31 | |
|
|
|||||
| Reporter: | sergek | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 3.0.14 | ||
| Product Build: | 3.0.14 | Resolution: | fixed | ||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 3.0.19 | ||
|
|
|||||
| Summary: | 0000314: mbean for session statistics | ||||
| Description: |
RSN-357 It would be helpful for performance and scalability information to see some of the following session statistics exposed via JMX: 1. Number of active sessions (again, just this one server) 2. Number of sessions created 3. Number of sessions destroyed (timed out) 4. Number of sessions destroyed (invalidated) 5. Number of session updates (in theory requires update to store) 6. Number of session transfers (actually required transfer to store) 7. Total session data size transfer 8. Average session size transfer (0000007 divided by 0000006) Ideally you could have JMX access (view and ideally control) over: - persistent path - always load session - always save session - cookie info - save on shutdown I don't know how JMX is expecting servers to persist changes, but at least being able to browse some of these settings is helpful, along with the statistics. |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||