Return-Path: Delivered-To: apmail-openjpa-users-archive@minotaur.apache.org Received: (qmail 11439 invoked from network); 8 Feb 2011 11:07:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 8 Feb 2011 11:07:26 -0000 Received: (qmail 15655 invoked by uid 500); 8 Feb 2011 11:07:26 -0000 Delivered-To: apmail-openjpa-users-archive@openjpa.apache.org Received: (qmail 14987 invoked by uid 500); 8 Feb 2011 11:07:22 -0000 Mailing-List: contact users-help@openjpa.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@openjpa.apache.org Delivered-To: mailing list users@openjpa.apache.org Received: (qmail 14978 invoked by uid 99); 8 Feb 2011 11:07:21 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Feb 2011 11:07:21 +0000 X-ASF-Spam-Status: No, hits=2.3 required=5.0 tests=FREEMAIL_FROM,RFC_ABUSE_POST,SPF_SOFTFAIL,T_TO_NO_BRKTS_FREEMAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: softfail (athena.apache.org: transitioning domain of s_sr_sadeghi@hotmail.com does not designate 216.139.236.26 as permitted sender) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Feb 2011 11:07:16 +0000 Received: from jim.nabble.com ([192.168.236.80]) by sam.nabble.com with esmtp (Exim 4.69) (envelope-from ) id 1PmlPL-0000VA-HA for users@openjpa.apache.org; Tue, 08 Feb 2011 03:06:55 -0800 Date: Tue, 8 Feb 2011 03:06:55 -0800 (PST) From: Sargol To: users@openjpa.apache.org Message-ID: <1297163215527-6003588.post@n2.nabble.com> In-Reply-To: References: <1261547510755-4207379.post@n2.nabble.com> <1261550108038-4207462.post@n2.nabble.com> <1261554890112-4207605.post@n2.nabble.com> <1434602a.538e375a.4b31dbb2.2802f@o2.pl> <1261565242656-4208087.post@n2.nabble.com> <1261567220110-4208182.post@n2.nabble.com> <1261593770488-4209997.post@n2.nabble.com> <1261668825845-4213546.post@n2.nabble.com> <1297089134972-6000447.post@n2.nabble.com> Subject: Re: EntityManager dosn't release connection in XA transactions MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi Milosz , Thank you for your reply. The sql log statements are enabled and I don't have any SELECT FOR UPDATE statements and there is an UPDATE statement so I can make sure that openjpa does not use pessimistic transaction. So, how can I find that for what reason the transaction has not been commited and why this exception has been raised. Here is the stack trace. It would be grateful if you could help me. Regards, Sargol >>>>>>>> Stack trace <<<<<<<<<<<< org.apache.openjpa.persistence.PersistenceException: ORA-02049: timeout: distributed transaction waiting for lock {prepstmnt 1631220936 UPDATE GC1ACCOUNT SET G1004BAL = ?, G1004VER = ?, TRCVER = ? WHERE G1004ID = ? AND TRCVER = ? [params=(double) 1902345.0, (double) 1296.0, (int) 1297, (long) 65996, (int) 1296]} [code=2049, state=42000] FailedObject: com.kishware.core.gl.data.Account-com.kishware.core.gl.data.Account-65996 at org.apache.openjpa.jdbc.sql.DBDictionary.narrow(DBDictionary.java:4232) at org.apache.openjpa.jdbc.sql.DBDictionary.newStoreException(DBDictionary.java:4197) at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:102) at org.apache.openjpa.jdbc.sql.SQLExceptions.getStore(SQLExceptions.java:72) at org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUpdate(PreparedStatementManagerImpl.java:131) at org.apache.openjpa.jdbc.kernel.BatchingPreparedStatementManagerImpl.flushAndUpdate(BatchingPreparedStatementManagerImpl.java:82) at org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushInternal(PreparedStatementManagerImpl.java:89) at org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flush(PreparedStatementManagerImpl.java:72) at org.apache.openjpa.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:543) at org.apache.openjpa.jdbc.kernel.ConstraintUpdateManager.flush(ConstraintUpdateManager.java:106) at org.apache.openjpa.jdbc.kernel.BatchingConstraintUpdateManager.flush(BatchingConstraintUpdateManager.java:59) at org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:89) at org.apache.openjpa.jdbc.kernel.AbstractUpdateManager.flush(AbstractUpdateManager.java:72) at org.apache.openjpa.jdbc.kernel.JDBCStoreManager.flush(JDBCStoreManager.java:717) at org.apache.openjpa.kernel.DelegatingStoreManager.flush(DelegatingStoreManager.java:130) ... 152 more Caused by: org.apache.openjpa.lib.jdbc.ReportingSQLException: ORA-02049: timeout: distributed transaction waiting for lock {prepstmnt 1631220936 UPDATE GC1ACCOUNT SET G1004BAL = ?, G1004VER = ?, TRCVER = ? WHERE G1004ID = ? AND TRCVER = ? [params=(double) 1902345.0, (double) 1296.0, (int) 1297, (long) 65996, (int) 1296]} [code=2049, state=42000] at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.wrap(LoggingConnectionDecorator.java:192) at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator.access$700(LoggingConnectionDecorator.java:57) at org.apache.openjpa.lib.jdbc.LoggingConnectionDecorator$LoggingConnection$LoggingPreparedStatement.executeUpdate(LoggingConnectionDecorator.java:866) at org.apache.openjpa.lib.jdbc.DelegatingPreparedStatement.executeUpdate(DelegatingPreparedStatement.java:269) at org.apache.openjpa.jdbc.kernel.JDBCStoreManager$CancelPreparedStatement.executeUpdate(JDBCStoreManager.java:1586) at org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.executeUpdate(PreparedStatementManagerImpl.java:151) at org.apache.openjpa.jdbc.kernel.PreparedStatementManagerImpl.flushAndUpdate(PreparedStatementManagerImpl.java:120) ... 162 more |#] -- View this message in context: http://openjpa.208410.n2.nabble.com/EntityManager-dosn-t-release-connection-in-XA-transactions-tp4205041p6003588.html Sent from the OpenJPA Users mailing list archive at Nabble.com.