Create an EJB2 SFSB with <clustered>true</clustered> that does not update itself on a method call. Create an external client that looks up the SFSB, calls home.create, then calls a method on the SFSB in a loop (waiting for input or using Thread.sleep between calls) Create a cluster of two EAP instances with the SFSB deployed. 1. Start instance1 2. Start the client to create the SFSB and call the SFSB 1 or more times 3. Start instance2 4. call the SFSB 1 or more times 5. Stop instance1 6. call the SFSB 1 or more times Before patch: step 6 fails with NoSuchObjectException After patch: step 6 succeeds and makes the call correctly

In previous versions of JBoss EAP 5 the state transfer for EJB2 stateful session beans occured before the service was listening for the data, so it was ignored. As a consequence the state transfer for EJB2 stateful session beans did not work. In this release the startup order dependencies specify services to start in the correct order. The state transfer for EJB2 stateful session beans now works correctly.