Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Major
Fix Version/s: 7.2.0.GA
Affects Version/s: 7.0.0.ER5
Component/s: EJB
Labels:
None

CDW devel_ack:
CDW docs_ack:
CDW pm_ack:
CDW qa_ack:
CDW release:
Target Release:

7.2.z.GA
Git Pull Request:
https://github.com/jbossas/jboss-eap7/pull/397
Steps to Reproduce:

Hide

To reproduce there could be used my tests prepared for WFLY testsuite. Check
https://github.com/ochaloup/jboss-as/commit/22bca417c183050dee3076d3989697b903a92b2d

Show
To reproduce there could be used my tests prepared for WFLY testsuite. Check https://github.com/ochaloup/jboss-as/commit/22bca417c183050dee3076d3989697b903a92b2d

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

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.

clones

WFLY-6271 SFSB methods can still be invoked after a calling transaction has rollbacked

Closed

is related to

JBEAP-3410 Wrong behaviour of transaction synchronization when txn is timeouted

Closed

WFLY-6212 Wrong behaviour of transaction synchronization when txn is timeouted

Closed

relates to

JBEAP-3448 [GSS](7.1.0) SessionSynchronization callbacks allow concurrent access to SFSB

Verified

Assignee:: Tomasz Adamski

Reporter:: Ryan Emerson

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Created:: 2016/02/24 9:13 AM

Updated:: 2021/10/24 6:26 AM

Resolved:: 2020/04/16 4:40 AM

Details

Description

Attachments

Issue Links

Activity

People

Dates