openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Curtis (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OPENJPA-2234) EntityManager instance creation needs TX activity
Date Tue, 09 Oct 2012 18:50:02 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-2234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472626#comment-13472626
] 

Rick Curtis commented on OPENJPA-2234:
--------------------------------------

Erik - Honestly, I'm not aware of any way to recover. I suspect I could log a warning, but
other parts of the runtime would blow chunks with a similar NPE due to the missing TM. It
seemed safer to detect this condition and fail fast.

It is unlikely that this change will make it into 2.0.x as that is a WebSphere managed branch...
but I'll shoot a note to the branch owner to see what he thinks.

                
> 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

Mime
View raw message