Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-19022

[GSS](7.3.z) WFLY-13307 - Different behaviour for concurrent StatefulSessionBean invocation

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.3.5.CR1
    • 7.0.9.GA, 7.2.7.GA
    • EJB
    • None
    • +
    • Hide

      Create a simple SFSB which cause the invocation to take longer than the 5sec timeout
      Invoke the same proxy concurrent and use a clustered environment (one server will do)

      Show
      Create a simple SFSB which cause the invocation to take longer than the 5sec timeout Invoke the same proxy concurrent and use a clustered environment (one server will do)

      According to the EJB contract a SFSB invocation is exclusive and the same instance can not be used concurrent.
      If done the invocation will wait to get the Lock for this and fail if the request takes too long.

      In case of a simple unclustered profile this is working and the exception is this:
      Exception in thread "main" javax.ejb.ConcurrentAccessTimeoutException: WFLYEJB0228: EJB 3.1 FR 4.3.14.1 concurrent access timeout on SimpleStatefulBean - could not obtain lock within 5000 MILLISECONDS

      In case of a clustered server environment this is hidden by Infinispan ERROR
      Exception in thread "main" javax.ejb.EJBException: org.infinispan.util.concurrent.TimeoutException: ISPN000299: Unable to acquire lock after 15 seconds for key InfinispanBeanKey(UUIDSessionID [634883dc-e8a3-452e-ac15-d9a4ad6856e9]) and requestor GlobalTx:t460:7. Lock is held by GlobalTx:t460:6

        1. simpleServer_72.log
          6 kB
        2. reproducer.zip
          41 kB
        3. clusteredServer_72.log
          15 kB

            pferraro@redhat.com Paul Ferraro
            rhn-support-wfink Wolf Fink
            Peter Mackay Peter Mackay
            Peter Mackay Peter Mackay
            Votes:
            0 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated:
              Resolved: