[
http://jira.jboss.com/jira/browse/JBSEAM-2436?page=comments#action_12402955 ]
Antoine Sabot-Durand commented on JBSEAM-2436:
----------------------------------------------
Sorry to bother you Peter, but I had the same problem and had to re-engineered all my
software to avoid storing entity in EJB3 session scoped components. I cannot say for sure
if it came from Seam 2.0 or Jboss 4.2.2 (I upgraded at he same time) but my software
worked fine before.
Today I'm no more concerned by this bug (I load and store all my entity in
conversation scoped EJB components) but with all the respect I have for you I'm a bit
worried to see how such a problem is "fixed" without further investigation.
Session-scoped SFSB which holds entities leaks memory
-----------------------------------------------------
Key: JBSEAM-2436
URL:
http://jira.jboss.com/jira/browse/JBSEAM-2436
Project: JBoss Seam
Issue Type: Bug
Components: EJB3
Affects Versions: 2.0.0.GA
Environment: Suse Linux, JBoss 4.2.2.GA, Java 1.6.03, PostgreSQL 8.2
Reporter: Susanne Jarl
Assigned To: Pete Muir
Fix For: 2.1.0.GA
Session-scoped SFSB which has entities in an object does not get destroyed. It leads to
memory leak in production. Please read:
http://www.jboss.org/index.html?module=bb&op=viewtopic&t=126542
The problem appeared after upgrading to Seam 2.0.0.GA. My code worked fine in Seam 1.2.1.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira