[jboss-jira] [JBoss JIRA] Closed: (EJBTHREE-949) Bean proxy in JNDI not properly refreshed when cluster topology changes

[Brian Stansberry (JIRA)]

     [ http://jira.jboss.com/jira/browse/EJBTHREE-949?page=all ]

Brian Stansberry closed EJBTHREE-949.
-------------------------------------

    Fix Version/s: EJB 3.0 RC11 - FD
       Resolution: Done

There were really 2 issues:

1) The server-side FamilyClusterInfo was not being refreshed when the cluster topology changed.  The HATarget was updated, so bean requests would pull down new targets, but the FCI ref held by the proxies would be out-of-date.

2) For SLSBs, the proxy needs to be rebound in JNDI, as JNDI holds a serialized version. Updating the FCI is insufficient as that won't affect the serialized proxy in JNDI.  This is not an issue for SFSBs, as the proxy isn't actually bound in JNDI; rather a ref to the proxy factory is.

Fix was the have the proxy factories implement DistributedReplicantManager.ReplicantListener and update the FCI (and JNDI for SLSB) when replicantsChanged() callback is invoked.

> Bean proxy in JNDI not properly refreshed when cluster topology changes
> -----------------------------------------------------------------------
>
>                 Key: EJBTHREE-949
>                 URL: http://jira.jboss.com/jira/browse/EJBTHREE-949
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: Clustering
>    Affects Versions: EJB 3.0 RC9 - FD, EJB 3.0 RC9 - Patch 1, AS 4.2.0 CR2
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: AS 4.2.0 GA, EJB 3.0 RC11 - FD
>
>
> When a change to the cluster topology occurs, the proxies in JNDI for the affected beans are not being updated.  Effect is the target list in the proxy always contains the members that were present when the bean was deployed and the proxy created.
> EJB2 has a process to rebind the proxy when a topology change occurs; EJB3 probably needs something similar.

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