|
If you were logged in you would be able to see more operations.
|
|
|
|
SessionMap would hold on to the request object (and then call getSession()) when it really only needs to hold on to the HttpSession object. This becomes a problem if you execute actions in the background and the request has been returned to the pool.
|
|
Description
|
SessionMap would hold on to the request object (and then call getSession()) when it really only needs to hold on to the HttpSession object. This becomes a problem if you execute actions in the background and the request has been returned to the pool. |
Show » |
| There are no comments yet on this issue.
|
|
Bug
Closed
Major
SessionMap holds on to requests when it doens't need to