Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 52361 invoked from network); 8 Dec 2010 22:22:26 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 8 Dec 2010 22:22:26 -0000 Received: (qmail 16846 invoked by uid 500); 8 Dec 2010 22:22:26 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 16762 invoked by uid 500); 8 Dec 2010 22:22:25 -0000 Mailing-List: contact dev-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@openjpa.apache.org Delivered-To: mailing list dev@openjpa.apache.org Received: (qmail 16754 invoked by uid 99); 8 Dec 2010 22:22:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Dec 2010 22:22:25 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Dec 2010 22:22:22 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id oB8MM0PF029688 for ; Wed, 8 Dec 2010 22:22:01 GMT Message-ID: <14616327.25561291846920802.JavaMail.jira@thor> Date: Wed, 8 Dec 2010 17:22:00 -0500 (EST) From: "Albert Lee (JIRA)" To: dev@openjpa.apache.org Subject: [jira] Created: (OPENJPA-1904) OptimisticLockException during refresh(*,PESSIMISTIC_*) with eagar fetch on relationship fields MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org OptimisticLockException during refresh(*,PESSIMISTIC_*) with eagar fetch on relationship fields ----------------------------------------------------------------------------------------------- Key: OPENJPA-1904 URL: https://issues.apache.org/jira/browse/OPENJPA-1904 Project: OpenJPA Issue Type: Bug Components: kernel Affects Versions: 2.0.2, 2.1.0, 2.2.0 Reporter: Albert Lee Assignee: Albert Lee Fix For: 2.1.0, 2.2.0 refresh with PESSIMISTIC_* lock on an entity with eagerly fetched relationship may cause an OptimisticLockException to be thrown. For example org.apache.openjpa.persistence.OptimisticLockException:This operation failed for some instances. See the nested exceptions array for details. FailedObject: suite.jpafvt.commonentities.hr.Manager-1 [java.lang.String] at org.apache.openjpa.kernel.BrokerImpl.throwNestedExceptions(BrokerImpl.java:2514) at org.apache.openjpa.kernel.BrokerImpl.refreshInternal(BrokerImpl.java:3064) at org.apache.openjpa.kernel.BrokerImpl.refresh(BrokerImpl.java:2953) at org.apache.openjpa.kernel.DelegatingBroker.refresh(DelegatingBroker.java:1126) at org.apache.openjpa.persistence.EntityManagerImpl.refresh(EntityManagerImpl.java:770) at org.apache.openjpa.persistence.EntityManagerImpl.refresh(EntityManagerImpl.java:752) at suite.r80.base.jpaspec.entitymanager.testlogic.RefreshLockTestLogic.testScenarioL001(RefreshLockTestLogic.java:188) ........... Caused by: org.apache.openjpa.persistence.OptimisticLockException: An optimistic lock violation was detected when flushing object instance "An optimistic lock violation was detected when locking object instance. [java.lang.String]" to the data store. This indicates that the object was concurrently modified in another transaction. FailedObject: 234 [java.lang.Long] at org.apache.openjpa.jdbc.kernel.MixedLockManager.optimisticLockInternal(MixedLockManager.java:116) at org.apache.openjpa.jdbc.kernel.PessimisticLockManager.lockInternal(PessimisticLockManager.java:111) at org.apache.openjpa.jdbc.kernel.MixedLockManager.lockInternal(MixedLockManager.java:72) at org.apache.openjpa.kernel.VersionLockManager.lock(VersionLockManager.java:84) at org.apache.openjpa.kernel.VersionLockManager.lock(VersionLockManager.java:70) at org.apache.openjpa.kernel.BrokerImpl.find(BrokerImpl.java:966) at org.apache.openjpa.kernel.BrokerImpl.find(BrokerImpl.java:902) at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.load(JDBCStoreManager.java:1041) at com.ibm.ws.persistence.jdbc.kernel.WsJpaJDBCStoreManager.load(WsJpaJDBCStoreManager.java:114) at org.apache.openjpa.jdbc.sql.AbstractResult.load(AbstractResult.java:280) at org.apache.openjpa.jdbc.sql.SelectImpl$SelectResult.load(SelectImpl.java:2380) at org.apache.openjpa.jdbc.meta.strats.RelationFieldStrategy.loadEagerJoin(RelationFieldStrategy.java:706) at org.apache.openjpa.jdbc.meta.FieldMapping.loadEagerJoin(FieldMapping.java:922) at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.load(JDBCStoreManager.java:1111) at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.load(JDBCStoreManager.java:1092) at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.load(JDBCStoreManager.java:1092) at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.load(JDBCStoreManager.java:1067) at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.load(JDBCStoreManager.java:688) at com.ibm.ws.persistence.jdbc.kernel.WsJpaJDBCStoreManager.load(WsJpaJDBCStoreManager.java:132) at org.apache.openjpa.kernel.DelegatingStoreManager.load(DelegatingStoreManager.java:117) at org.apache.openjpa.kernel.ROPStoreManager.load(ROPStoreManager.java:78) at org.apache.openjpa.kernel.StateManagerImpl.loadFields(StateManagerImpl.java:3045) at org.apache.openjpa.kernel.StateManagerImpl.load(StateManagerImpl.java:451) at org.apache.openjpa.kernel.BrokerImpl.transactional(BrokerImpl.java:3608) at org.apache.openjpa.kernel.VersionLockManager.optimisticLockInternal(VersionLockManager.java:111) at org.apache.openjpa.jdbc.kernel.MixedLockManager.optimisticLockInternal(MixedLockManager.java:108) at org.apache.openjpa.jdbc.kernel.PessimisticLockManager.lockInternal(PessimisticLockManager.java:111) at org.apache.openjpa.jdbc.kernel.MixedLockManager.lockInternal(MixedLockManager.java:72) at org.apache.openjpa.kernel.VersionLockManager.lock(VersionLockManager.java:84) at org.apache.openjpa.kernel.BrokerImpl.refreshInternal(BrokerImpl.java:3014) ... 36 more -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.