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 1CC479B8B for ; Fri, 23 Sep 2011 17:07:05 +0000 (UTC) Received: (qmail 92275 invoked by uid 500); 23 Sep 2011 17:07:04 -0000 Delivered-To: apmail-openjpa-users-archive@openjpa.apache.org Received: (qmail 92242 invoked by uid 500); 23 Sep 2011 17:07:04 -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 92233 invoked by uid 99); 23 Sep 2011 17:07:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Sep 2011 17:07:04 +0000 X-ASF-Spam-Status: No, hits=2.1 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,SPF_NEUTRAL,T_TO_NO_BRKTS_FREEMAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: 216.139.236.26 is neither permitted nor denied by domain of chintan4181@gmail.com) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Sep 2011 17:06:58 +0000 Received: from jim.nabble.com ([192.168.236.80]) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1R79Cv-0007hK-Mq for users@openjpa.apache.org; Fri, 23 Sep 2011 10:06:37 -0700 Date: Fri, 23 Sep 2011 10:06:37 -0700 (PDT) From: chintan4181 To: users@openjpa.apache.org Message-ID: <1316797597700-6824982.post@n2.nabble.com> In-Reply-To: <1316795388548-6824864.post@n2.nabble.com> References: <1316709419562-6820989.post@n2.nabble.com> <1316709774235-6821026.post@n2.nabble.com> <1316710208159-6821051.post@n2.nabble.com> <1316710312786-6821063.post@n2.nabble.com> <1316712441152-6821196.post@n2.nabble.com> <1316788778663-6824457.post@n2.nabble.com> <1316791294605-6824609.post@n2.nabble.com> <1316792510119-6824688.post@n2.nabble.com> <1316794266412-6824797.post@n2.nabble.com> <1316795388548-6824864.post@n2.nabble.com> Subject: Re: Multiple concurrent threads attempted to access a single broker MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org It is single thread but transaction is span across various operations. Here is business scenario 1) EJB A has save( functionDO) 2) It extract Obj1 from functionDO and call our framework.save(obj1) - framework will persist into db and then close em. (code is as per previous post) 3) it extract obj2 from functionDO and call our framework.save(obj2) - framework will persist into db and then close em. (code is as per previous post) This is our threading model. can you please suggest reliable way to handle this? thanks Chintan -- View this message in context: http://openjpa.208410.n2.nabble.com/Multiple-concurrent-threads-attempted-to-access-a-single-broker-tp6820896p6824982.html Sent from the OpenJPA Users mailing list archive at Nabble.com.