Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-10937

State transfer for EJB2 SFSB replication doesn't work

    XMLWordPrintable

    Details

    • Steps to Reproduce:
      Hide

      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

      Show
      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
    • Affects:
      Release Notes
    • Release Notes Text:
      Hide
      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.
      Show
      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.
    • Release Notes Docs Status:
      Documented as Resolved Issue
    • Docs QE Status:
      NEW

      Description

      State transfer for EJB2 SFSB does not work at all, due to deployment timing issues.

      HASessionStateService (which handles EJB2 SFSB replication) registers itself for state transfers with ClusterPartition after the state transfer has already completed. When the transfer happens, the data is discarded because there are no listeners for it.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  dereed Dennis Reed
                  Reporter:
                  dereed Dennis Reed
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: