So my feeling is that we need to get to the bottom of the "WARNING: Connection not closed by caller" line. Do you have any idea what part of your framework is issuing that statement, and under what situations it can happen? Can you get a stack from when it is issued?
> 2007-03-27 14:57:07,160 : SEVERE : Logger.log : system > exception in business method:javax.ejb.EJBException: Conflict > writing entity bean Similarly, do you know more details about where this is failing? The exception seems to be happening because of concurrent access to entity beans (i.e., not JPA entities). Are you using BMP entity beans backed by JPA entities or something like that? Is it possible to get a stack from where this message is logged, or at least more details about what the biz method in question is? (None of the messages you've posted look like anything that OpenJPA would ever generate.) -Patrick -- Patrick Linskey BEA Systems, Inc. _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. > -----Original Message----- > From: Hans J. Prueller [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 28, 2007 11:48 AM > To: open-jpa-dev > Subject: WARNING: Connection not closed by caller - messages > produced byOpenJPA? > > Hi together, > > 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. > > The lookup/creation of the EntityManager instances is > synchronizing with the JTA TXs as you suggested some weeks ago > on this list. > > After having a test server up and running for some days, we > are encountering lots of those messages: > > WARNING: Connection not closed by caller > > Suddenly (some hours later), a transactions fails: > > 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 > > > 2007-03-27 14:57:07,160 : SEVERE : Logger.log : system > exception in business method:javax.ejb.EJBException: Conflict > writing entity bean > > 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? > > regards, > Hans > Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
