Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1099434

Summary:	Verify Java Transaction API (JTA) integration
Product:	[JBoss] JBoss Enterprise Portal Platform 6	Reporter:	Martin Weiler <mweiler>
Component:	Documentation	Assignee:	mposolda
Status:	CLOSED UPSTREAM	QA Contact:	vramik
Severity:	high	Docs Contact:	JPP Docs Team <jpp-docs>
Priority:	high
Version:	6.1.1	CC:	laszlo.van.den.hoek, mposolda, nato060919801, vramik
Target Milestone:	ER03
Target Release:	6.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Some customers wanted to use JTA integration, which was supported in JBoss Portal 5.2, but could not find any configuration documentation for the feature. JTA integration has been present since version 6.0.0 of the product. Documentation was updated to reflect the new directory structure of the platform, and to ensure all information pertaining to configuring JTA was available in the product documentation.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-02-10 03:35:52 UTC	Type:	Task
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Martin Weiler 2014-05-20 10:09:03 UTC

Description of problem:
Customer is interested in using JTA for the IDM integration. Please validate if the instructions from the wiki - https://community.jboss.org/wiki/JTAIntegrationWithGateIn - still apply to JPP 6, and if the setup works.

Background information: 
"I have several custom subclasses of UserEventListener/UserProfileEventListener/MembershipEventListener tied to the events that trigger when performing CRUD operations on users in the PicketLink IDM included with Portal 6. These listeners then forward the user information to our legacy systems over JMS so they stay in sync.

With the default setup, the JMS transaction is not tied to the IDM Hibernate transaction: messages start arriving before the user has been fully saved and the IDM transaction commits. This will be an issue when the PicketLink transaction rolls back, as the JMS messages would still be sent and processed, leading to inconsistent state across systems.

Therefore, I need to enable JTA on the IDM."


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 mposolda 2014-06-04 08:47:59 UTC

The JTA still works with latest GateIn and documentation is updated in GateIn reference guide https://docs.jboss.org/author/display/GTNPORTAL38/JTA+integration . No changes were needed in code.

Comment 4 mposolda 2014-06-13 09:59:53 UTC

Hi Jared,

Some feedback to your docs. I have just notes to last section 8.4.6 :

- The "<local-tx-datasource>" should be now changed to "<datasource>" . Name "<local-tx-datasource>" was for old EAP5. In EAP6 it was renamed to "<datasource>" . There are 2 occurences of this.

- The first yellow part starting with "See the JBoss Transactions Programmer's Guide..." can be whole removed. There is no JBoss Transactions Programmer's guide for EAP6 AFAIK, this was just for EAP5. And you already mentioned what LROC is, so it is sufficient like you documented it without need to link any other docs IMO.

- The second yellow part: I think the first sentence could be kept as it is "JBoss Transaction Service sees an attempt to enlist a second such resource as an error and terminates the transaction." I would remove the second sentence about migration (I think it came to EAP5 docs because of migrations from EAP4 to EAP5)

Comment 5 mposolda 2014-06-13 10:13:32 UTC

And yes "<driver>" element should go as child element under "<drivers>"

Comment 6 Jared MORGAN 2014-06-16 00:21:16 UTC

(In reply to mposolda from comment #4)
> Hi Jared,
> 
> Some feedback to your docs. I have just notes to last section 8.4.6 :
> 
> - The "<local-tx-datasource>" should be now changed to "<datasource>" . Name
> "<local-tx-datasource>" was for old EAP5. In EAP6 it was renamed to
> "<datasource>" . There are 2 occurences of this.
> 
> - The first yellow part starting with "See the JBoss Transactions
> Programmer's Guide..." can be whole removed. There is no JBoss Transactions
> Programmer's guide for EAP6 AFAIK, this was just for EAP5. And you already
> mentioned what LROC is, so it is sufficient like you documented it without
> need to link any other docs IMO.
> 
> - The second yellow part: I think the first sentence could be kept as it is
> "JBoss Transaction Service sees an attempt to enlist a second such resource
> as an error and terminates the transaction." I would remove the second
> sentence about migration (I think it came to EAP5 docs because of migrations
> from EAP4 to EAP5)

Thanks for the review, Marek. All changes incorporated. Ready for close-off.

Comment 13 Red Hat Bugzilla 2025-02-10 03:35:52 UTC

This product has been discontinued or is no longer tracked in Red Hat Bugzilla.