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

[Brian Stansberry (JIRA)]

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: AS 4.2.0 CR2, EJB 3.0 RC9 - Patch 1, EJB 3.0 RC9 - FD
            Reporter: Brian Stansberry
         Assigned To: Brian Stansberry
             Fix For: AS 4.2.0 GA


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