openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christiaan (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OPENJPA-453) Evicting embedded object nullifies statemanager
Date Mon, 08 Jun 2009 07:58:07 GMT

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

Christiaan commented on OPENJPA-453:
------------------------------------

David,
I definitely like your proposal on making this more scalable and high-performant. I indeed
use the same scenario of multiple threads reading and one writing and also discovered that
there is hardly any benefit for this due to the current locking mechanism. 

One other note, you mention that the application should do some locking for the embedded objects.
However, to avoid deadlock problems, the application needs to have access to the same read/write
locks as OpenJPA uses. 

> Evicting embedded object nullifies statemanager
> -----------------------------------------------
>
>                 Key: OPENJPA-453
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-453
>             Project: OpenJPA
>          Issue Type: Bug
>         Environment: Kodo 4.1.4, Ms sql server 2005, jTDS 1.2, jdk 1.6
>            Reporter: Christiaan
>            Assignee: Ravi P Palacherla
>         Attachments: OpenJPABug453Embedded.zip, openJPATestCase.zip, TestCaseEvictEmbedded.zip
>
>
> I am noticing the following behaviour: If evict() is called on an embedded
> object the statemanager is nullified which is in contrast to non-embedded
> objects. Subsequently, calling JDOHelper.getPersistenceManager() on the
> evicted embedded object returns null. Is this the correct behaviour?

-- 
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