Uploaded image for project: 'EJB 3.0'
  1. EJB 3.0
  2. EJBTHREE-1053

State changes in @PrePassivate don't get replicated if passivate before replication is disabled

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: AS 4.2.2.GA
    • Fix Version/s: None
    • Component/s: Clustering
    • Labels:
      None

      Description

      Passivation doesn't trigger replication, so a bean might get passivated on 1 node and not on another. If the bean provider does state changes in pre-passivate these will not be visible on the other node.

      By default replication does trigger passivation, so a bean first gets passivated and then replicated. Thus the problem only occurs if passivate before replication is explicitly disabled.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  pferraro Paul Ferraro
                  Reporter:
                  wolfc Carlo de Wolf
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated: