Back to bug 1005110
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Jaikiran Pai | 2013-09-06 09:06:33 UTC | Status | NEW | ASSIGNED |
| Version | 6.0.1 | |||
| Brian Stansberry | 2013-09-08 03:58:01 UTC | Status | ASSIGNED | MODIFIED |
| Target Release | --- | EAP 6.2.0 | ||
| CC | brian.stansberry | |||
| Target Milestone | --- | Pending | ||
| Paul Gier | 2013-09-17 20:17:02 UTC | Status | MODIFIED | ON_QA |
| Target Milestone | Pending | ER1 | ||
| Jan Martiska | 2013-09-18 08:29:49 UTC | Status | ON_QA | VERIFIED |
| Brian Stansberry | 2013-10-07 15:36:00 UTC | CC | brian.stansberry | |
| John Skeoch | 2013-10-23 23:03:09 UTC | CC | dimitris | |
| John Skeoch | 2013-10-23 23:05:17 UTC | Assignee | jpai | dimitris |
| Dimitris Andreadis | 2013-10-24 18:28:00 UTC | Assignee | dimitris | david.lloyd |
| Dana Mison | 2013-11-26 01:56:30 UTC | CC | dmison | |
| Doc Text | In some situations, asynchronous EJB calls could result in the deployment’s classloader being "leaked". This occurred because the execute method could lead to new thread creation. When this occurs the new thread assigns itself the context classloader of the parent thread, which would be the classloader of the deployment. To prevent this the Thread Context Classloader (TCCL) is set to `null` before the execute method is invoked, and then restored afterwards. Asynchronous EJB calls can no longer result in deployment classloader leaks. |
|||
| Dana Mison | 2013-11-26 01:58:19 UTC | Doc Text | In some situations, asynchronous EJB calls could result in the deployment’s classloader being "leaked". This occurred because the execute method could lead to new thread creation. When this occurs the new thread assigns itself the context classloader of the parent thread, which would be the classloader of the deployment. To prevent this the Thread Context Classloader (TCCL) is set to `null` before the execute method is invoked, and then restored afterwards. Asynchronous EJB calls can no longer result in deployment classloader leaks. | In some situations, asynchronous EJB calls could result in the deployment's classloader being "leaked". This occurred because the execute method could lead to new thread creation. When this occurs the new thread assigns itself the context classloader of the parent thread, which would be the classloader of the deployment. To prevent this the Thread Context Classloader (TCCL) is set to `null` before the execute method is invoked, and then restored afterwards. Asynchronous EJB calls can no longer result in deployment classloader leaks. |
| mark yarborough | 2013-12-15 16:55:31 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | CURRENTRELEASE | ||
| Last Closed | 2013-12-15 11:55:31 UTC | |||
| Dana Mison | 2014-05-27 01:30:08 UTC | CC | dmison |
Back to bug 1005110