Bug 955506

Summary: Connections not registered correctly for inner TX when Outer TX is suspended,
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: dstephan
Component: EJBAssignee: Jaikiran Pai <jpai>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.0.1CC: brian.stansberry, dimitris, jawilson, jdoyle, jmartisk, jolee, jpederse, mharvey, myarboro
Target Milestone: ER6   
Target Release: EAP 6.1.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-06-11 20:57:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 955508, 958296    

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.