[ https://issues.apache.org/jira/browse/OPENJPA-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472421#comment-13472421 ]
Rick Curtis commented on OPENJPA-2234: -------------------------------------- Committed revision 1396043 to trunk. Now we'll throw the following exception when we encounter a nullTransactionManager. <openjpa-2.3.0-SNAPSHOT-r422266:1393779M fatal internal error> org.apache.openjpa.util.InternalException: Received a null javax.transaction.TransactionManager from the openjpa.ManagedRuntime "org.apache.openjpa.ee.TestNullTransactionManagerFromRuntime$ManagedRuntimeNullTransactionManager@64686468". at org.apache.openjpa.kernel.AbstractBrokerFactory.syncWithManagedTransaction(AbstractBrokerFactory.java:727) at org.apache.openjpa.kernel.BrokerImpl.initialize(BrokerImpl.java:391) at org.apache.openjpa.kernel.BrokerImpl.initialize(BrokerImpl.java:325) > 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 > Assignee: Rick Curtis > Fix For: 2.3.0 > > > 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 For more information on JIRA, see: http://www.atlassian.com/software/jira