openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fernando (JIRA)" <j...@apache.org>
Subject [jira] Updated: (OPENJPA-794) issues with closing/opening entity manager (slices) (can't seem to be able to create multiple entityManagers )
Date Thu, 27 Nov 2008 00:22:44 GMT

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

Fernando updated OPENJPA-794:
-----------------------------

    Attachment: log.txt

A log of the failing run.  The first web request works fine ( you can see copious amounts
of logs as it gets objects, etc etc ).  The second request fails from the go and every db
access after, complaining that the EntityManager has already been closed, even though this
was a fresh request.

that request ends around: 2008-11-26 16:18:17,570

the second request starts right after at: 2008-11-26 16:18:34,334


> issues with closing/opening entity manager (slices) (can't seem to be able to create
multiple entityManagers )
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: OPENJPA-794
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-794
>             Project: OpenJPA
>          Issue Type: Bug
>          Components: kernel
>    Affects Versions: 2.0.0
>            Reporter: Fernando
>            Priority: Critical
>         Attachments: log.txt
>
>
> So, for each of my web requests I open an entitymanager at the begining, and close it
at the end, something like this:
> EntityManager pm = pmf.createEntityManager();
> try {
>  chain.filter(...);
> }
> finally {
>  pm.close();
> }
> And this works perfectly without slices.  But when I turn on slices, this fails.  The
first request works fine, but the second requests complains that the EntityManager has already
been closed.  So it seems to be caching the EntityManager from the previous request...  can
someone please help me figure out how to fix this??
> I'll attach the log.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message