Return-Path: Delivered-To: apmail-openjpa-users-archive@locus.apache.org Received: (qmail 56166 invoked from network); 22 Jan 2009 16:45:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 22 Jan 2009 16:45:51 -0000 Received: (qmail 39012 invoked by uid 500); 22 Jan 2009 16:45:50 -0000 Delivered-To: apmail-openjpa-users-archive@openjpa.apache.org Received: (qmail 38993 invoked by uid 500); 22 Jan 2009 16:45:50 -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 38982 invoked by uid 99); 22 Jan 2009 16:45:49 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Jan 2009 08:45:49 -0800 X-ASF-Spam-Status: No, hits=2.4 required=10.0 tests=HTML_MESSAGE,SPF_PASS,WHOIS_MYPRIVREG X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of techhusky@gmail.com designates 209.85.219.20 as permitted sender) Received: from [209.85.219.20] (HELO mail-ew0-f20.google.com) (209.85.219.20) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Jan 2009 16:45:42 +0000 Received: by ewy13 with SMTP id 13so3302553ewy.9 for ; Thu, 22 Jan 2009 08:45:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=DZlmu1VdBUIl5qtvkSTSbIrHf26ic0chjjcJCa7ctzo=; b=ffeAJ1wpjKgYJzF/+FUmDRwvmZkiEmI4075vHxDk5aXcEm99i/sKT2fd/sW3pqCLmA siysreNagVnuyLJwpPDqmqkk4rlU0wpzlgr8M0aomO5HQ1BWddZZ+pUyMtPgcysCtTtX rxwNBvcAJtMkI5a3HELnEmarMaRDOnc+MfRBo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=YtoIhJTHKEZ6tMubWu1mZTeOIIlW06XEvY9bnxgozOs4XKIZDyabfo13uZUJkzBL4N XqOxtaaz8DcGwovRqZgJbDNr6B8hh0yDr2DMvDkv5QM+LkRQ2elNep8BB6s/yI9R9VcE dwbhc6UN3Qygmsh6yLYFimfG/eYh7TmwL1zdM= MIME-Version: 1.0 Received: by 10.103.160.10 with SMTP id m10mr1363106muo.50.1232642720201; Thu, 22 Jan 2009 08:45:20 -0800 (PST) In-Reply-To: <1232526832891-2191081.post@n2.nabble.com> References: <1232526832891-2191081.post@n2.nabble.com> Date: Thu, 22 Jan 2009 10:45:20 -0600 Message-ID: Subject: Re: using UserTransaction problem From: Jeremy Bauer To: users@openjpa.apache.org Content-Type: multipart/alternative; boundary=0016e65bc1ce78fbf9046114fff9 X-Virus-Checked: Checked by ClamAV on apache.org --0016e65bc1ce78fbf9046114fff9 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi, If you are using UserTransaction, does your SLSB use bean managed transactions? In EJB 3.0, container managed transactions are the default, so TX configuration is very easy to overlook. Depending on the app server, using UserTransaction within a container managed tx bean will likely have ill effects. If you are certain that transactions are bean managed, are there any places where you may be starting a global TX but not completing it (in a web module, perhaps)? There are many other possibilities as well, but I'd start with these. If everything looks good, please send more details - such as the app server you are using, OpenJPA version, and more details about your app - and if possible, test code. -Jeremy On Wed, Jan 21, 2009 at 2:33 AM, is_maximum wrote: > > Hi > I am using UserTransaction in my stateless session bean and got this error > and all the process will stop > > ERROR - The stateless session bean started a transaction but did not > complete it. > > there is a method in which some other private methods is being called. > > can anyone help me out > -- > View this message in context: > http://n2.nabble.com/using-UserTransaction-problem-tp2191081p2191081.html > Sent from the OpenJPA Users mailing list archive at Nabble.com. > > --0016e65bc1ce78fbf9046114fff9--