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

Bug 834635

Summary:	JBoss cache used for picketlink should be JTA-aware
Product:	[JBoss] JBoss Enterprise Portal Platform 5	Reporter:	mposolda
Component:	Portal	Assignee:	mposolda
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	5.2.1.ER02, 5.2.2.CR01	CC:	epp-bugs, mvecera, vramik
Target Milestone:	---
Target Release:	5.2.x
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	CAUSE: Currently JBoss Cache used for Picketlink IDM is not aware of JTA. This could mean for example, that rollback of JTA transaction won't rollback JBoss Cache records, added during this JTA transaction. WORKAROUND: Uncomment TransactionManagerLookup in configuration file gatein.ear/02portal.war/WEB-INF/conf/organization/picketlink-idm/jboss-cache.xml: <transaction transactionManagerLookupClass="org.jboss.cache.transaction.JBossStandaloneJTAManagerLookup" /> Problem is that implementing this workaround is introducing another two problems described in bugs 841320 and 840917. So applying workaround is not recommended for now.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-02-10 03:20:11 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:	793816
Bug Blocks:

Description mposolda 2012-06-22 15:56:52 UTC

Currently JBoss Cache used for Picketlink IDM is not aware of JTA. This could mean for example, that rollback of JTA transaction won't rollback JBoss Cache records, added during this JTA transaction.

Example steps to reproduce:
- Configure EPP for JTA according to instructions https://community.jboss.org/wiki/JTAIntegrationWithGateIn
- Login as john, Go to OrganizationManagementPortlet and try to add new group. Type some name of new group (for example "newgroup") and click "Save". Now what is done is:
-- New JTA transaction is started
-- New group is created into Picketlink IDM database
-- Picketlink IDM sends query for obtain new list of groups. New group "mynewgroup" is included in the query result. And result groups are saved into Picketlink IDM cache.
-- Now let's say that JTA transaction is rolled-back because of timeout. All changes related to "mynewgroup" are cleaned from DB, but items in PL IDM JBoss cache are not rolled-back but they are still here. So there is still record about the group "mynewgroup".

Comment 1 Michal Vanco 2012-07-17 11:53:20 UTC

JBossStandaloneJTAManagerLookup is now added at picketlink JBC configuration files.

Comment 2 mposolda 2012-08-13 11:12:13 UTC

Issue is reverted in 5.2.2 CR01 as it's causing regressions 841320 and 840917. So configuration of TransactionManagerLookup was commented after all.
We need to verify scenarios described in 841320 and 840917 as well when fixing this one.

Thing is that when TransactionManagerLookup is uncommented and JBoss Cache is JTA-aware, then IDMUserListAccess added into IntegrationCache is sometimes lost after commit of JTA transaction and old instance of IDMUserListAccess is restored. Proper fix will require further investigation at JBoss Cache level.  

Simple application for test this issue: https://github.com/mposolda/jcr-transaction-test

Comment 3 mposolda 2012-08-13 11:15:42 UTC

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
CAUSE: Currently JBoss Cache used for Picketlink IDM is not aware of JTA. This could mean for example, that rollback of JTA transaction won't rollback JBoss Cache records, added during this JTA transaction.

WORKAROUND: Uncomment TransactionManagerLookup in configuration file gatein.ear/02portal.war/WEB-INF/conf/organization/picketlink-idm/jboss-cache.xml:

<transaction
transactionManagerLookupClass="org.jboss.cache.transaction.JBossStandaloneJTAManagerLookup" />

Problem is that implementing this workaround is introducing another two problems described in bugs 841320 and 840917. So applying workaround is not recommended for now.

Comment 5 Red Hat Bugzilla 2025-02-10 03:20:11 UTC

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