You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@openjpa.apache.org by "Michael Dick (JIRA)" <ji...@apache.org> on 2013/07/10 04:16:46 UTC

[jira] [Resolved] (OPENJPA-696) Cache TransactionSynchronizationRegistry per EMF (vs JVM)

     [ https://issues.apache.org/jira/browse/OPENJPA-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Dick resolved OPENJPA-696.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.3.0

Committed patch - it's safe as far as I know. If it produces problems we can revert and cancel this issue. 
                
> Cache TransactionSynchronizationRegistry per EMF (vs JVM)
> ---------------------------------------------------------
>
>                 Key: OPENJPA-696
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-696
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: kernel
>    Affects Versions: 1.0.0, 1.0.1, 1.0.2, 1.0.3, 1.1.0, 1.2.0
>            Reporter: Kevin Sutter
>            Assignee: Michael Dick
>             Fix For: 2.3.0
>
>         Attachments: OPENJPA-696.patch.txt
>
>
> Discussed in OpenJPA forum first:  http://n2.nabble.com/TransactionSynchronizationRegistry-reference-cached-permanently-td727197.html#a727197
> This Issue is requesting that we cache the reference for the TransactionSynchronizationRegistry in the EMF instead of per JVM.  This would be similar to what we did with the TransactionManager in the past.  Reference the forum postings for background and justification on the request.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira