Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-14167

Concurrent @Stateful EJB invocations to different cluster members do not respect @AccessTimeout

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Major
    • None
    • 21.0.1.Final
    • Clustering, EJB
    • None
    • Undefined
    • ---
    • ---

    Description

      Currently, @Stateful EJB sychronization is handled by the StatefulSessionSynchronizationInterceptor.  However, this mechanism is not cluster aware.  Consequently, if a client makes concurrent invocations to a given EJB on multiple cluster members, synchronization is handled by the EJB cache itself, ignoring any AccessTimeout defined by the bean or method.

      Attachments

        Issue Links

          relates to

          Bug - A problem that impairs or prevents the functions of the product. WFLY-13307 Different behaviour for concurrent StatefulSessionBean invocation

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

              pferraro@redhat.com Paul Ferraro
              pferraro@redhat.com Paul Ferraro
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated: