[jboss-jira] [JBoss JIRA] (AS7-4905) Call to @Remove method on abstract superclass of Stateful bean does not perform as expected

[jaikiran pai (JIRA)]

     [ https://issues.jboss.org/browse/AS7-4905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

jaikiran pai updated AS7-4905:
------------------------------

       Fix Version/s: 7.1.3.Final (EAP)
                      7.2.0.Alpha1
    Git Pull Request: https://github.com/jbossas/jboss-as/pull/2392, https://github.com/jbossas/jboss-as/pull/2393  (was: https://github.com/jbossas/jboss-as/pull/2392, https://github.com/jbossas/jboss-as/pull/2393)
     Forum Reference: https://community.jboss.org/message/738238#738238  (was: https://community.jboss.org/message/738238#738238)

    
> Call to @Remove method on abstract superclass of Stateful bean does not perform as expected
> -------------------------------------------------------------------------------------------
>
>                 Key: AS7-4905
>                 URL: https://issues.jboss.org/browse/AS7-4905
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: EJB
>    Affects Versions: 7.1.0.Final, 7.1.1.Final, 7.1.2.Final (EAP)
>         Environment: W7 64-bit
>            Reporter: Michael McGovern
>            Assignee: jaikiran pai
>             Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1
>
>         Attachments: sfsb-test.zip
>
>
> If a Stateful bean has an abstract superclass with the @Remove method (and this method is an implementation of a method in the @Local interface) then a call to this method does NOT cause the bean to be destroyed.
> Causes OOM issues.
> (Only by having the @Remove method in each concrete sub class does the destroy happen)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira