Return-Path: Delivered-To: apmail-incubator-open-jpa-dev-archive@locus.apache.org Received: (qmail 4180 invoked from network); 28 Mar 2007 18:53:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 28 Mar 2007 18:53:35 -0000 Received: (qmail 76306 invoked by uid 500); 28 Mar 2007 18:53:42 -0000 Delivered-To: apmail-incubator-open-jpa-dev-archive@incubator.apache.org Received: (qmail 76285 invoked by uid 500); 28 Mar 2007 18:53:42 -0000 Mailing-List: contact open-jpa-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: open-jpa-dev@incubator.apache.org Delivered-To: mailing list open-jpa-dev@incubator.apache.org Received: (qmail 76272 invoked by uid 99); 28 Mar 2007 18:53:42 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Mar 2007 11:53:42 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of hans.prueller@gmx.net designates 213.165.64.20 as permitted sender) Received: from [213.165.64.20] (HELO mail.gmx.net) (213.165.64.20) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 28 Mar 2007 11:53:34 -0700 Received: (qmail invoked by alias); 28 Mar 2007 18:53:12 -0000 Received: from cm56-213-37.liwest.at (EHLO [192.168.0.6]) [86.56.213.37] by mail.gmx.net (mp036) with SMTP; 28 Mar 2007 20:53:12 +0200 X-Authenticated: #299902 X-Provags-ID: V01U2FsdGVkX18dXNAqVwAdrLdrbHFAt7nlEA4Ri1tATrVaTGlV06 ibcmeSGCOE+Obj Subject: Re: WARNING: Connection not closed by caller - messages produced by OpenJPA? From: "Hans J. Prueller" To: open-jpa-dev@incubator.apache.org In-Reply-To: <1175107659.4922.3.camel@burns> References: <1175107659.4922.3.camel@burns> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-c8ASDDJ9suDmxgengytf" Date: Wed, 28 Mar 2007 20:53:12 +0200 Message-Id: <1175107992.4922.9.camel@burns> Mime-Version: 1.0 X-Mailer: Evolution 2.8.1 X-Y-GMX-Trusted: 0 X-Virus-Checked: Checked by ClamAV on apache.org --=-c8ASDDJ9suDmxgengytf Content-Type: multipart/alternative; boundary="=-t83Ds+otX8URSt9UXunY" --=-t83Ds+otX8URSt9UXunY Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Sorry, I forgot to add the following fact - which will be of MOST interest obviously: - analysing the logfiles where the conflicting TXs occur, it seems that there are currently 2 THREAD RUNNING IN PARALLEL. - each thread is working on definitely different data, so a deadlock should not really be possible=20 but I think I can remember that somebody mentioned that OpenJPA is not safe for multithreaded usage by default and that some special parameter has to be set in perstence.xml ? But if I understood the discussion right, this was just if different EMF's are using multithreaded, not the EM's - that's why I did not yet activate this multithreaded feature.=20 Is this also the case for the behaviour I described? (application managed JPA, outside a java ee 5 container, but running inside a java ee 1.4 container utilizing its JTA managed transactions; multithreaded environment). any ideas? Hans Am Mittwoch, den 28.03.2007, 20:47 +0200 schrieb Hans J. Prueller: > Hi together, >=20 > I succeeded in integrating OpenJPA into our J2EE1.4 container, running > side-by-side within the same JTA transactions as > container managed EJB2.1 CMP entity beans. >=20 > The lookup/creation of the EntityManager instances is synchronizing > with the JTA TXs as you suggested some weeks ago > on this list. >=20 > After having a test server up and running for some days, we are > encountering lots of those messages: >=20 > WARNING: Connection not closed by caller >=20 > Suddenly (some hours later), a transactions fails: >=20 > 2007-03-27 14:57:07,097 : WARNING : Logger.log : Conflict with > bb14:38:0:01fb60a716b0bed67c...80c679: > 2007-03-27 14:57:07,113 : WARNING : Logger.log : Current Tx is > bb14:38:0:01fb60a716b0bed67c...32a266: > 2007-03-27 14:57:07,144 : WARNING : Logger.log : You should not > modify the bean without a transactional context >=20 >=20 > 2007-03-27 14:57:07,160 : SEVERE : Logger.log : system exception > in business method:javax.ejb.EJBException: Conflict writing entity > bean >=20 > Somehow this HAS to be related to the OpenJPA integration, but the > server was up for at least a day and running fine until above error > occured. Any idea how this bad conflict could be caused?=20 >=20 > regards, > Hans --=-t83Ds+otX8URSt9UXunY Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable Sorry, I forgot to add the following fact - which will be of MOST interest = obviously:

- analysing the logfiles where the conflicting TXs occur, it seems that the= re are currently 2 THREAD RUNNING IN PARALLEL.
- each thread is working on definitely different data, so a deadlock should= not really be possible

but I think I can remember that somebody mentioned that OpenJPA is not safe= for multithreaded usage by default and that
some special parameter has to be set in perstence.xml ? But if I understood= the discussion right, this was just if different
EMF's are using multithreaded, not the EM's - that's why I did not yet acti= vate this multithreaded feature.

Is this also the case for the behaviour I described? (application managed J= PA, outside a java ee 5 container, but running inside
a java ee 1.4 container utilizing its JTA managed transactions; multithread= ed environment).

any ideas?

Hans

Am Mittwoch, den 28.03.2007, 20:47 +0200 schrieb Hans J. Prueller:
Hi together,

I succeeded in integrating OpenJPA into our J2E= E1.4 container, running side-by-side within the same JTA transactions as
container managed EJB2.1 CMP entity beans.

The lookup/creation of the EntityManager instan= ces is synchronizing with the JTA TXs as you suggested some weeks ago
on this list.

After having a test server up and running for s= ome days, we are encountering lots of those messages:

WARNING: Connection not closed by caller=

Suddenly (some hours later), a transactions fai= ls:

2007-03-27 14:57:07,097 : WARNING :  Logge= r.log :    Conflict with bb14:38:0:01fb60a716b0bed67c...80c6= 79:
2007-03-27 14:57:07,113 : WARNING :  Logge= r.log :    Current Tx is bb14:38:0:01fb60a716b0bed67c...32a2= 66:
2007-03-27 14:57:07,144 : WARNING :  Logge= r.log :    You should not modify the bean without a transact= ional context


2007-03-27 14:57:07,160 : SEVERE :  Logger= .log :    system exception in business method:javax.ejb.EJBE= xception: Conflict writing entity bean

Somehow this HAS to be related to the OpenJPA i= ntegration, but the server was up for at least a day and running fine until= above error
occured. Any idea how this bad conflict could b= e caused?

regards,
Hans
--=-t83Ds+otX8URSt9UXunY-- --=-c8ASDDJ9suDmxgengytf Content-Type: application/pgp-signature; name=signature.asc Content-Description: Dies ist ein digital signierter Nachrichtenteil -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQBGCrmY47JBnmYpPoURAnIPAJ9vqUI0xS3ZdAtOAZlRImZHhlGWcgCfR40F flPaoqKOtd8CAwPTHhCxoFE= =dRdp -----END PGP SIGNATURE----- --=-c8ASDDJ9suDmxgengytf--