[
https://issues.apache.org/jira/browse/OPENJPA-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Dick updated OPENJPA-696:
---------------------------------
Attachment: OPENJPA-696.patch.txt
I think the root cause here is that the xxManagedRuntime classes are static
members of the AutomaticManagedRuntime class. The attached patch initializes
them in AutomaticManagedRuntime's constructor.
I've done some sniff testing and it looks like it will address the issue. I
wasn't able to reproduce the exact problem reported though. If there's an easy
way to test the patch with OpenEJB I'm happy to try that out as well.
> 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
> 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.
-
You can reply to this email to add a comment to the issue online.
