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

[GSS](7.0.z) StatefulSessionBean fail after 31 invocations

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.0.7.CR2, 7.0.7.GA
    • 7.0.4.GA, 7.0.5.GA
    • EJB
    • Hide

      See attached reproducer based on ejb-multi-server quickstart (to set up the environment easily)
      The reproducer description is in README_ForReproducer

      Show
      See attached reproducer based on ejb-multi-server quickstart (to set up the environment easily) The reproducer description is in README_ForReproducer
    • EAP 7.0.7

    Description

      Multiple invocations of a StatefulSessionBean will end in a infinispan exception if the invocation is from server(SLSB)->server(SFSB).
      Here the standalone client contains a loop which invoke the SLSB, the SLSB simple invoke the SFSB on another (clustered)server. The invocation is sticky - so the cluster might not have an effect - and the same SFSB instance is used as expected.
      The invocatino fail for the 32. invocation.

      If a standalone client invoke the SFSB directly it seems correct working.

      It seems that the transaction handling between the server EJB's might be the cause.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-10217 [GSS](7.1.0) StatefulSessionBean fail after 31 invocations

          • 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.
          • Verified
          is caused by

          Bug - A problem that impairs or prevents the functions of the product. JBTM-2848 Transaction .equals() methods do not comply with specification

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. WFLY-8524 OwnableReentrantLock can't recognize two different but equal transaction objects as the same transaction

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-3432 [QA](7.2.z) IllegalStateException "not in a valid state to be invoking cache operations on" in two cluster test

          • 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.
          • Verified
          links to

          Web Link IllegalStateException after multiple remote SFSB invocations

          Activity

            People

              pferraro@redhat.com Paul Ferraro
              rhn-support-bmaxwell Brad Maxwell
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: