Bug 955506 - Connections not registered correctly for inner TX when Outer TX is suspended,
Summary: Connections not registered correctly for inner TX when Outer TX is suspended,
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: EJB
Version: 6.0.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ER6
: EAP 6.1.0
Assignee: Jaikiran Pai
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 955508 958296
TreeView+ depends on / blocked
 
Reported: 2013-04-23 08:00 UTC by dstephan
Modified: 2018-12-01 16:08 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-11 20:57:45 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker AS7-6974 0 Major Resolved CachedConnectionManager interceptor isn't applied consistently on EJB invocations 2015-11-16 07:42:40 UTC

Description dstephan 2013-04-23 08:00:06 UTC 
Description of problem:

The setup is

MDB/CMT ->  Use db connection ->  SLSB/BMT ->  UT.begin() 

Connection is acquired in MDB and enlisted in outer TX and registered
with the Cached Connection Manager. Outer TX is suspended.
When inner TX is started the CCM tries the register the connection
that is registered with the outer transaction into the inner one.
Comment 4 Jan Martiska 2013-05-03 08:48:07 UTC 
verified with EAP 6.1.0.ER6
Comment 5 Jesper Pedersen 2013-06-05 12:09:17 UTC 
Shouldn't this have been closed as part of EAP 6.1.0 ?
Comment 6 Jan Martiska 2013-06-05 12:23:53 UTC 
@Jesper: not sure what you mean. It is set to VERIFIED, which is the final state for fixed bugs in middleware products.
Comment 7 Jesper Pedersen 2013-06-05 12:27:00 UTC 
That can't be - if so it is wrong. The issue is showing up in my list, but I consider it closed.
Comment 8 jolee 2013-06-11 20:57:45 UTC 
@Jan,  final state should end up being CLOSED, CURRENTRELEASE for this.  Since 6.1 has been delivered, it should be good to change.
Note You need to log in before you can comment on or make changes to this bug.