Bug #715 (closed)
Opened 12 years ago
Closed 11 years ago
Memory leak since RenderingBean.destroy() is not being called.
| Reported by: | jamoore | Owned by: | cxallan |
|---|---|---|---|
| Priority: | critical | Cc: | cxallan, jburel |
| Sprint: | n.a. | ||
| Total Remaining Time: | n.a. |
Description
Re: http://docs.jboss.org/jbossas/jboss4guide/r4/html/ch5.chapter.html#ch5.container-cache.fig :
An alternative cache policy implementation is the
org.jboss.ejb.plugins.NoPassivationCachePolicy class, which simply never passivates
instances. It uses an in-memory HashMap implementation that never discards instances unless
they are explicitly removed. This class does not support any of the cache-policy-conf
configuration elements.
Since RenderingBean uses the NoPassivationCachePolicy (see #205 and #193), @PreDestroy is never getting called (despite our assumptions). This leads to a memory leak.
Best fix is probably to remove the live Hibernate objects from the RE (see #334)
Change History (3)
comment:1 Changed 11 years ago by jmoore
- Owner changed from jmoore to callan
comment:2 Changed 11 years ago by cxallan
- Status changed from new to assigned
My impression is that this was resolved by the changes in milestone:3.0-Beta2.3 but I'll look at it again.
comment:3 Changed 11 years ago by cxallan
- Resolution set to fixed
- Status changed from assigned to closed
Resolved in milestone:3.0-Beta2.3.
Passing this off to you, Senor Chris.