Back to bug 1039585
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Shay Matasaro | 2013-12-09 14:39:51 UTC | Link ID | Red Hat Bugzilla 1030681 | |
| Shay Matasaro | 2013-12-09 14:40:55 UTC | Link ID | JBoss Issue Tracker WFLY-898 | |
| Shay Matasaro | 2013-12-09 14:41:32 UTC | Link ID | JBoss Issue Tracker WFLY-406 | |
| Radoslav Husar | 2013-12-09 15:04:49 UTC | CC | rhusar | |
| Ian Page Hands | 2013-12-10 18:34:53 UTC | CC | ihands | |
| Scott Dodson | 2013-12-10 20:53:59 UTC | CC | sdodson | |
| Paul Ferraro | 2014-01-03 21:48:10 UTC | CC | dereed | |
| Status | NEW | POST | ||
| Target Release | --- | EAP 6.3.0 | ||
| Shay Matasaro | 2014-01-10 16:35:08 UTC | Blocks | 1030681 | |
| Blocks | 1051591 | |||
| Kabir Khan | 2014-01-12 10:14:22 UTC | Status | POST | MODIFIED |
| CC | kkhan | |||
| Target Milestone | --- | DR0 | ||
| mark yarborough | 2014-01-13 14:49:55 UTC | CC | myarboro | |
| Summary | Clustered session memory leaking | [GSS] (6.3) Clustered session memory leaking | ||
| Paul Gier | 2014-02-11 23:53:16 UTC | Status | MODIFIED | ON_QA |
| Richard JanÃk | 2014-02-19 15:21:00 UTC | Status | ON_QA | VERIFIED |
| CC | rjanik | |||
| Brad Maxwell | 2014-02-20 22:08:16 UTC | CC | bmaxwell | |
| Summary | [GSS] (6.3) Clustered session memory leaking | [GSS] (6.3.0) Clustered session memory leaking | ||
| Scott Dodson | 2014-03-24 14:41:40 UTC | CC | paul.ferraro | |
| Flags | needinfo?(paul.ferraro) | |||
| Scott Mumford | 2014-05-05 05:02:05 UTC | Flags | needinfo?(paul.ferraro) | |
| CC | smumford | |||
| Flags | needinfo?(paul.ferraro) | |||
| Paul Ferraro | 2014-05-14 15:24:20 UTC | Doc Text | Cause: When a distributed web session is active, the session manager of the owning node creates and holds a lock object. If the web session expires (i.e. is not explicitly invalidated) the lock object is never released/destroyed. Consequence: As web sessions continue to expire, the residual lock objects accumulate in memory. Eventually, this will lead to an OutOfMemoryException. The only recourse is to redeploy the web application. Fix: The lock objects are now properly released and destroyed following web session expiration. Result: OutOfMemoryExceptions no longer occur as a result of web session expiration. | |
| Flags | needinfo?(paul.ferraro) | |||
| Scott Mumford | 2014-05-14 23:41:24 UTC | Doc Text | Cause: When a distributed web session is active, the session manager of the owning node creates and holds a lock object. If the web session expires (i.e. is not explicitly invalidated) the lock object is never released/destroyed. Consequence: As web sessions continue to expire, the residual lock objects accumulate in memory. Eventually, this will lead to an OutOfMemoryException. The only recourse is to redeploy the web application. Fix: The lock objects are now properly released and destroyed following web session expiration. Result: OutOfMemoryExceptions no longer occur as a result of web session expiration. | Previous versions of JBoss EAP 6 contained a bug that could lead to an OutOfMemoryException in distributed web sessions. The exception was encountered if a web session expired without the lock objects created by the session manager being released or destroyed. As web sessions continued to expire, the residual lock objects accumulated in memory. Eventually, this would lead to an OutOfMemoryException. The only recourse was to redeploy the web application. In this release of the product the lock objects are properly released and the OutOfMemory no longer presents |
| mark yarborough | 2014-06-28 15:40:37 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | CURRENTRELEASE | ||
| Last Closed | 2014-06-28 11:40:37 UTC | |||
| Aaron Ogburn | 2014-08-15 15:50:51 UTC | CC | aogburn | |
| Aaron Ogburn | 2014-08-15 15:59:41 UTC | Blocks | 1130600 |
Back to bug 1039585