[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2436) Session-scoped SFSB which holds entities leaks memory

Michael Kostadinovich (JIRA) jira-events at lists.jboss.org
Mon Mar 2 11:51:22 EST 2009

    [ https://jira.jboss.org/jira/browse/JBSEAM-2436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12454992#action_12454992 ] 

Michael Kostadinovich commented on JBSEAM-2436:

We were plagued by the same problem, after some investigation we found a fix/workaround:

session scoped SFSBs that get passivated, never get removed from the memory nor get released by SimpleStatefulCache. Workaround is to switch to NoPassivationCache, either by using the @Cache(org.jboss.ejb3.cache.NoPassivationCache.class) annotation on your class or change the default cache implementation to NoPassivationCache (see http://www.jboss.org/community/docs/DOC-9656 ).

Additionally (still unconfirmed, I will have to do more testing to confirm this), if you have an abstract class which defines a @Remove @Destroy method and your SFSBs extend this class, Seam might/will not call the @Destroy at the end of the session.

> Session-scoped SFSB which holds entities leaks memory
> -----------------------------------------------------
>                 Key: JBSEAM-2436
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-2436
>             Project: Seam
>          Issue Type: Bug
>          Components: EJB3, Performance and Scalability
>    Affects Versions: 2.0.0.GA
>         Environment: Suse Linux, JBoss 4.2.2.GA, Java 1.6.03, PostgreSQL 8.2
>            Reporter: Susanne Jarl
>            Assignee: Jay Balunas
>             Fix For: The future
> 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: https://jira.jboss.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the seam-issues mailing list