Return-Path: Delivered-To: apmail-openjpa-dev-archive@www.apache.org Received: (qmail 44968 invoked from network); 10 Jul 2007 17:18:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Jul 2007 17:18:12 -0000 Received: (qmail 8170 invoked by uid 500); 10 Jul 2007 17:18:14 -0000 Delivered-To: apmail-openjpa-dev-archive@openjpa.apache.org Received: (qmail 8148 invoked by uid 500); 10 Jul 2007 17:18:14 -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 8139 invoked by uid 99); 10 Jul 2007 17:18:14 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Jul 2007 10:18:14 -0700 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=RCVD_IN_SORBS_WEB,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of mprudhomapache@gmail.com designates 64.233.166.180 as permitted sender) Received: from [64.233.166.180] (HELO py-out-1112.google.com) (64.233.166.180) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Jul 2007 10:18:10 -0700 Received: by py-out-1112.google.com with SMTP id f31so2720669pyh for ; Tue, 10 Jul 2007 10:17:49 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:mime-version:in-reply-to:references:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer:sender; b=KIxrMlb5Nn8HR+WwZEAntIFXyk6uSy8Vhgr+seVbRELHh2+pOlG4VMalZYAgvVlE6TlPpCGjC4NA6+QZj0CQqhQsJKtZMNo11aX0mXrTLmyhPrgKXeQ88sZSMiyaNdTMam9s1TFTtMrloR7mLvHNhePZJbzK5xTFmg+HwarQ2Qs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:mime-version:in-reply-to:references:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer:sender; b=glhiAIZaoiuIzbsJG6XOgH8HKSIrZCrxHAXgBRZO4EvGknt3IYD037XB0Ze70gQIG/NwsrsGMtYweHKmvK0nzxVf7/wnGnpUSC+DDxXjeEv7lcZKJIQA7FB04sIRmYE+2jEfRmAte/VzDFX3yyjLB+1akDsfYtxZ0xlS9VMhwhc= Received: by 10.141.34.12 with SMTP id m12mr1327517rvj.1184087869151; Tue, 10 Jul 2007 10:17:49 -0700 (PDT) Received: from ?192.168.15.100? ( [66.248.222.34]) by mx.google.com with ESMTP id c14sm7929522rvf.2007.07.10.10.17.47 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 10 Jul 2007 10:17:48 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v752.3) In-Reply-To: <469399D0.7000904@skally.de> References: <469399D0.7000904@skally.de> Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: quoted-printable From: Marc Prud'hommeaux Subject: Re: DataCache and OptimisticVerificationException Date: Tue, 10 Jul 2007 10:17:14 -0700 To: dev@openjpa.apache.org X-Mailer: Apple Mail (2.752.3) Sender: Marc Prud'hommeaux X-Virus-Checked: Checked by ClamAV on apache.org Frank- Are you saying that you are using OpenJPA from multiple JVMs, but =20 don't have a RemoteCommitProviders configured? If so, then this isn't =20= unexpected, since the RemoteCommitProvider is used to broadcast =20 messages about cache changes to other JVMs (or other =20 EntityManagerFactories in the same JVM). In the same-JVM case, if you just set RemoteCommitProvider to "sjvm", =20= does the problem go away? If not, can you describe in a little more =20 detail your configuration and the cases where it fails? On Jul 10, 2007, at 7:38 AM, Frank Jagla wrote: > Hello, > > using the Kodo 4 DataCache sometimes we see =20 > OptimisticVerificationExceptions: > > <2|true|0.9.5-incubating> > kodo.jdo.OptimisticVerificationException: Optimistic locking errors =20= > were > detected when flushing to the data store. The following objects =20 > may have > been concurrently modified in another transaction: > [de.logas.vera.SdgZollPositionImpl-62455866] > > We switch off the DataCache, and the exception vanishes. > kodo.DataCache =3D false > > I think this happens in a single JVM without RemoteCommitProviders =20 > involved and > synchronisation issues between JVMs and their DataCaches. > > > --=20 > > Mit freundlichen Gr=FC=DFen > Frank Jagla > > -------------------------------------------- > > skally - Gesellschaft f=FCr Logistik- und Informationssysteme mbH, =20 > Konrad-Zuse-Stra=DFe 10, 44801 Bochum > Amtsgericht Bochum, HRB 4297; USt-ID-Nr. DE198585621; =20 > Gesch=E4ftsf=FChrer: Reimund Ott, Wolfgang A. Vitt > Telefon: 0234 - 9708 500 Telefax: 0234-9708 501 E-Mail: =20 > service@skally.de > > Haftungsausschluss: > Diese Nachricht enth=E4lt vertrauliche Informationen und ist =20 > ausschlie=DFlich f=FCr den Adressaten bestimmt. Falls Sie die Daten =20= > irrt=FCmlich erhalten haben, nehmen Sie bitte Kontakt mit dem =20 > Absender auf und l=F6schen Sie die Daten auf jedem Computer und =20 > Datentr=E4ger. Die skally GmbH ist nicht verantwortlich f=FCr die =20 > ordnungsgem=E4=DFe, vollst=E4ndige und verz=F6gerungsfreie =DCbertragung= der =20 > Nachricht. Der Inhalt der E-Mail ist nur rechtsverbindlich, wenn er =20= > unsererseits durch einen Brief oder ein Fax entsprechend best=E4tigt =20= > wird.