[hibernate-issues] [Hibernate-JIRA] Created: (HHH-6062) Infinispan as JTA synchronization participant

Galder Zamarreno (JIRA) noreply at atlassian.com
Mon Mar 28 06:21:08 EDT 2011


Infinispan as JTA synchronization participant
---------------------------------------------

                 Key: HHH-6062
                 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-6062
             Project: Hibernate Core
          Issue Type: Improvement
          Components: caching (L2)
            Reporter: Galder Zamarreno
            Assignee: Galder Zamarreno


Infinispan should use synchronization rather than XA in order to take advantage of 2PC optimisations. 

For example, if 2LC is a synchronization and it fails to update the 2LC, it could remove the entry that failed to update but the transaction could still commit assuming that the database (XA) did it's job. A unit test for this would be handy.

More tangible benefits need to be investigated.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/hibernate/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the hibernate-issues mailing list