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

(7.2.0) SFSB methods can still be invoked after a calling transaction has rolledback after timeout

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.2.0.GA
    • 7.0.0.ER5
    • EJB
    • None

    Description

      Issue concerns not discarding SFSB instance when transaction rollback after transaction timeout happens.

      When transaction is timed-out then you can experience EJBTransactionRolledbackException (child of `EjbException which is child of RuntimeException) being thrown. At that point SFSB should be removed and following call on the same instance of SFSB should fail (NoSuchEjbException would be expected).

      But currently the SFSB is not discarded after transaction timeout and methods of SFSB could be called again.

      Attachments

        Issue Links

          clones

          Bug - A problem that impairs or prevents the functions of the product. WFLY-6271 SFSB methods can still be invoked after a calling transaction has rollbacked

          • 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.
          • Closed
          is related to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-3410 Wrong behaviour of transaction synchronization when txn is timeouted

          • 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.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. WFLY-6212 Wrong behaviour of transaction synchronization when txn is timeouted

          • 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.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-3448 [GSS](7.1.0) SessionSynchronization callbacks allow concurrent access to SFSB

          • Critical - To be worked on immediately following BLOCKER issues.
          • Verified

          Activity

            People

              tadamski@redhat.com Tomasz Adamski
              remerson@redhat.com Ryan Emerson
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: