[ http://jira.jboss.com/jira/browse/EJBTHREE-69?page=history ]
     
Kabir Khan closed EJBTHREE-69:
------------------------------

    Resolution: Done

> Clustered SFSB: load balancing works, failover does not
> -------------------------------------------------------
>
>          Key: EJBTHREE-69
>          URL: http://jira.jboss.com/jira/browse/EJBTHREE-69
>      Project: EJB 3.0
>         Type: Bug
>  Environment: XP
> JBoss 5.0.0 alpha
>     Reporter: Keyur Shah
>     Assignee: Kabir Khan
>      Fix For: Preview 5

>
>
> Ref: http://jboss.com/index.html?module=bb&op=viewtopic&t=60214
> Consider this simple example:
> [code]
> @Stateful
> @org.jboss.ejb3.remoting.Clustered        
> public class SFSBClusterBean implements SFSBCluster, Serializable {
>     
>     transient String state = null;
>     String dto = null;
>     transient boolean modified = false;
>     public String getState() {
>         System.out.println("getState");
>         return state;
>     }
>     public void updateState(String newState) {
>         System.out.println("updateState");
>         state = newState;
>         modified = true;
>     }
>     
>     @PrePassivate public void passivate() {
>         System.out.println("passivate");
>         dto = state;
>         state = null;
>         modified = false;
>     }
>     
>     @PostActivate public void activate() {
>         System.out.println("activate");
>         state = dto;
>         dto = null;
>         modified = false;
>     }
>     
>     public boolean isModified() {
>         System.out.println("isModified");
>         return modified;
>     }
>     
> }
> [/code]
> I have setup a cluster with 2 nodes... When I run multiple clients, it load 
> balances well... However, when I shutdown one of the nodes, the clients 
> accessing that node also die... 
> I built a similar example in EJB 2.1 and it load balances as well as fails 
> over correctly.
> One difference I noted was that while the EJB 2.1 bean's isModified() was 
> called (and subsequently, ejbPassivate() if the bean was modified) after 
> every client method call, the isModified() method is never called for EJB3 
> (and so by extension neither is the passivate() method called).

-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
JBoss-Development mailing list
JBoss-Development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to