[
https://issues.jboss.org/browse/GTNPORTAL-2482?page=com.atlassian.jira.pl...
]
RH Bugzilla Integration commented on GTNPORTAL-2482:
----------------------------------------------------
mposolda(a)redhat.com made a comment on [bug
834635|https://bugzilla.redhat.com/show_bug.cgi?id=834635]
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.
JBoss cache used for picketlink should be JTA-aware
---------------------------------------------------
Key: GTNPORTAL-2482
URL:
https://issues.jboss.org/browse/GTNPORTAL-2482
Project: GateIn Portal
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Identity integration
Affects Versions: 3.3.0.Final
Reporter: Marek Posolda
Assignee: Marek Posolda
Fix For: 3.4.0.Final
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".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira