Uploaded image for project: 'Seam 2'
  1. Seam 2
  2. JBSEAM-2264

@Observer with PostSetVariable produces Concurrent exceptions in a conversation scoped stateful bean

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Rejected
    • Affects Version/s: 2.0.0.GA
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Environment:

      java 6_u03, jboss-4.2.1GA, jboss-seam-2.0.0.GA

      Description

      A method with an @Observer that listens to a postSetVariable event:

      @Name("myModule")
      @Scope(ScopeType.CONVERSATION)
      @Stateful
      public class MyModule implements ModuleLocal, ModuleRemote {

      @Observer("org.jboss.seam.postSetVariable.foo")
      public void process()

      { /* Do something */ }

      }

      produces a stack trace:
      [SeamPhaseListener] uncaught exception
      javax.el.ELException: javax.ejb.EJBTransactionRolledbackException: no concurrent calls on stateful bean 'jboss.j2ee:service=EJB3,name=MyModule' (EJB3 4.3.13)

      According to 3.1.10. Concurrency model of the 2.0.0 documentation:
      Finally, Seam enforces a single thread /per conversation per process/ model for the conversation context by serializing concurrent requests in the same long-running conversation context.
      The two 'per' is kind of confusing, but it seems that since Seam is serializing concurrent requests, this issue should not occur.

      Will create demo app shortly.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                dhinojosa Daniel Hinojosa
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: