[jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1368) StatefulBeanContext doesn't override equals()

[Galder Zamarreno (JIRA)]

    [ https://jira.jboss.org/jira/browse/EJBTHREE-1368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12444548#action_12444548 ] 

Galder Zamarreno commented on EJBTHREE-1368:
--------------------------------------------

Brian, thanks for fixing this which indirectly fixes EJBTHREE-1661.

I'll port hashCode() and equals() implementations over to EAP.

> StatefulBeanContext doesn't override equals()
> ---------------------------------------------
>
>                 Key: EJBTHREE-1368
>                 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1368
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: core
>    Affects Versions: AS 4.2.0 GA, AS 4.2.1.GA, AS 4.2.2.GA, AS 5.0.0.Beta4
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>             Fix For: AS 5.0.0.CR1
>
>
> Really a side issue to EJBTHREE-1367.
> StatefulBeanContext does not override Object.equals(), so it relies on object identity. This breaks if the context has been serialized and deserialized (i.e. passivated/activated or replaced via replication from another node).
> Side issue to EJBTHREE-1367 since the place where SBC.equals() matters is in the extra cache maintained by InfinitePool.activeList. This equals issue makes matters worse, since because of it if an SFSB has been serialized/deserialized, when it is removed the ref won't get cleared from the InfinitePool.activeList.  The list will keep growing until the bean is undeployed.

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