Return-Path: X-Original-To: apmail-openjpa-users-archive@minotaur.apache.org Delivered-To: apmail-openjpa-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 53E3B65F2 for ; Mon, 20 Jun 2011 21:14:07 +0000 (UTC) Received: (qmail 24090 invoked by uid 500); 20 Jun 2011 21:14:07 -0000 Delivered-To: apmail-openjpa-users-archive@openjpa.apache.org Received: (qmail 24057 invoked by uid 500); 20 Jun 2011 21:14:07 -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 24049 invoked by uid 99); 20 Jun 2011 21:14:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Jun 2011 21:14:06 +0000 X-ASF-Spam-Status: No, hits=2.0 required=5.0 tests=SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Jun 2011 21:14:01 +0000 Received: from jim.nabble.com ([192.168.236.80]) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1QYlmv-00080Y-6V for users@openjpa.apache.org; Mon, 20 Jun 2011 14:13:41 -0700 Date: Mon, 20 Jun 2011 14:13:41 -0700 (PDT) From: Pinaki Poddar To: users@openjpa.apache.org Message-ID: <1308604421189-6497485.post@n2.nabble.com> In-Reply-To: References: <1307462440299-6450253.post@n2.nabble.com> <1307585874602-6456295.post@n2.nabble.com> <1307997312694-6471718.post@n2.nabble.com> Subject: Re: concurrent thread exception plus deadlock on delete statement using slice MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mike, This one would require time to fix. I do not have bandwidth to touch this one right now, nor do I have access to solid testing infrastructure to validate my changes against risk of regression. Please file a JIRA and hopefully someone (including you:) may supply a patch. For a quick fix, one may try this route in ...openjpa.persistence.PersistenceExceptions$RuntimeExceptionTranslator { - public RuntimeException translate(RuntimeException re) + public synchronized RuntimeException translate(RuntimeException re) ----- Pinaki -- View this message in context: http://openjpa.208410.n2.nabble.com/concurrent-thread-exception-plus-deadlock-on-delete-statement-using-slice-tp6449143p6497485.html Sent from the OpenJPA Users mailing list archive at Nabble.com.