Details
Bug
Major
Description
When a session expires in ICEfaces, the server inserts a <session-expired> response in the response queue, and waits to receive /block/dispose-view requests for all Views found in the session. There are a couple of problems with the current approach:
1) Session disposal is a serial affair with a timeout of 15 seconds. This is a problem in JMeter test environments that can't easily perform the shutdown protocol, resulting in (for example) a 25 minute wait to fully dispose of 100 expired sessions, beyond the initial session expiry time.
2) The code doesn't differentiate between synchronous and asynchronous mode, and if the connection is synchronous, there are no agents in the browser able to complete the protocol, resulting in the full wait penalty for every session. If new sessions are created at a rate of > 1 every 15 seconds, this manifests as a memory leak.
1) Session disposal is a serial affair with a timeout of 15 seconds. This is a problem in JMeter test environments that can't easily perform the shutdown protocol, resulting in (for example) a 25 minute wait to fully dispose of 100 expired sessions, beyond the initial session expiry time.
2) The code doesn't differentiate between synchronous and asynchronous mode, and if the connection is synchronous, there are no agents in the browser able to complete the protocol, resulting in the full wait penalty for every session. If new sessions are created at a rate of > 1 every 15 seconds, this manifests as a memory leak.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
| Field | Original Value | New Value |
|---|---|---|
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Fix Version/s | 1.7.2 [ 10130 ] | |
| Resolution | Fixed [ 1 ] |
| Fix Version/s | 1.7.2RC1 [ 10140 ] | |
| Fix Version/s | 1.7.2 [ 10130 ] |
| Fix Version/s | 1.7.2 [ 10130 ] | |
| Fix Version/s | 1.7.2RC1 [ 10140 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |