Bug 955506 – Connections not registered correctly for inner TX when Outer TX is suspended,

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

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,

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	JBoss Enterprise Application Platform 6
Classification:	JBoss
Component:	EJB (Show other bugs)
Sub Component:
Version:	6.0.1
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	ER6
Target Release:	EAP 6.1.0
Assigned To:	Jaikiran Pai
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	955508 958296
	Show dependency tree / graph

Reported:	2013-04-23 04:00 EDT by dstephan
Modified:	2015-08-26 16:23 EDT (History)
CC List:	9 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2013-06-11 16:57:45 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
JBoss Issue Tracker	AS7-6974	Major	Resolved	CachedConnectionManager interceptor isn't applied consistently on EJB invocations	2015-11-16 02:42 EST

Groups: None (edit)

Description dstephan 2013-04-23 04:00:06 EDT

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 04:48:07 EDT

verified with EAP 6.1.0.ER6

Comment 5 Jesper Pedersen 2013-06-05 08:09:17 EDT

Shouldn't this have been closed as part of EAP 6.1.0 ?

Comment 6 Jan Martiska 2013-06-05 08:23:53 EDT

@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 08:27:00 EDT

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 16:57:45 EDT

@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.