[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2379) Hot deployment issues: multiple events fired, old classes don't get GC'd, hotdeploy not atomic

[Allon Rauer (JIRA)]

Hot deployment issues: multiple events fired, old classes don't get GC'd, hotdeploy not atomic
----------------------------------------------------------------------------------------------

                 Key: JBSEAM-2379
                 URL: http://jira.jboss.com/jira/browse/JBSEAM-2379
             Project: JBoss Seam
          Issue Type: Bug
    Affects Versions: 2.0.0.GA
            Reporter: Allon Rauer


I love the hot-deploy feature, and i'm even considering using it in production to be able to change and add code without bringing down out services.

However, there are several big issues with it currently:
1. Observer methods are tracked by  the Init component, but never get cleared upon re-deploy. This leads to invocation of the event listeners in both the old components and the "replacement" hot-deployed components. It also leads to leaking of class objects, as the old Method/Class references don't get released upon re-deploy, eventually leading to a perm-gen out-of-mem.
2. Hot-deploy isn't atomic. If a request comes in concurrent w/ the redeploy, that request may see a mix of old components and re-deployed components, possibly leading to erroneous behavior.

-- 
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