[
https://issues.apache.org/jira/browse/OPENJPA-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13418289#comment-13418289
]
Rick Curtis commented on OPENJPA-2234:
--------------------------------------
Erik -
Thanks for the thorough SO writeup. Unfortunately I think you're assessment of
where the problems lies isn't quite correct. If you were to look at the OpenJPA
code:
boolean syncWithManagedTransaction(BrokerImpl broker, boolean begin) {
Transaction trans;
try {
ManagedRuntime mr = broker.getManagedRuntime();
TransactionManager tm = mr.getTransactionManager();
trans = tm.getTransaction(); <<< line 720
you will notice that the NPE is coming from not having a TransactionManager,
not that you don't have a transaction.
I see the following line in your persistence configuration :
<entry key="openjpa.ManagedRuntime"
value="invocation(TransactionManagerMethod=com.atomikos.icatch.jta.TransactionManagerImp.getTransactionManager)"
/>
We can start out with an easy one, is the getTransactionManager method static?
If not, try changing that.
Thanks,
Rick
> EntityManager instance creation needs TX activity
> -------------------------------------------------
>
> Key: OPENJPA-2234
> URL: https://issues.apache.org/jira/browse/OPENJPA-2234
> Project: OpenJPA
> Issue Type: Bug
> Affects Versions: 2.0.1
> Environment: - JDK 1.5
> - Spring 3.1.1.RELEASE
> - Spring Data JPA 1.1 GA (issue confirmed on version 1.0.3)
> - Atomikos 3.7.0
> - OpenJPA 2.0.1
> - DB2 9.7
> Reporter: Erik Kis
>
> While working with Spring Data, we came across a potential bug in OpenJPA.
> The bug was provoked by a query lookup module in Spring Data JPA, but it has
> its roots in AbstractBrokerFactory class, which seems to require transaction
> existence in order to create EntityManager (which is contrary to JPA spec).
> I have already been in touch with Spring Data JPA author (where I filed a bug
> against Spring Data JPA) who actually pointed me to file a bug here.
> I have extensively documented my findings on this thread
> (http://stackoverflow.com/questions/10688040/spring-data-jpa-fails-to-invoke-jtatransactionmanager),
> so I'll rather post the link, instead of repeating the whole thing here.
> All that being said, I am not entirely sure what actually happened and am no
> authority whatsoever on JPA spec.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
