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 203689F0B for ; Fri, 3 Feb 2012 20:09:28 +0000 (UTC) Received: (qmail 56371 invoked by uid 500); 3 Feb 2012 20:09:27 -0000 Delivered-To: apmail-openjpa-users-archive@openjpa.apache.org Received: (qmail 56301 invoked by uid 500); 3 Feb 2012 20:09:27 -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 56293 invoked by uid 99); 3 Feb 2012 20:09:27 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Feb 2012 20:09:27 +0000 X-ASF-Spam-Status: No, hits=3.5 required=5.0 tests=HTML_MESSAGE,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of kwsutter@gmail.com designates 209.85.217.174 as permitted sender) Received: from [209.85.217.174] (HELO mail-lpp01m020-f174.google.com) (209.85.217.174) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Feb 2012 20:09:20 +0000 Received: by lbom4 with SMTP id m4so845421lbo.33 for ; Fri, 03 Feb 2012 12:08:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=FhTOv8I1mB5V7klCrBylmKLgt1tqwSGUAD1NSOj+EnY=; b=FQZvcyLvABsSYIxfmF0df1VZXYPGrRnXWI46s3Qxh3aLSErIAkB7nLjqbmob4VSCHh Z1ruQJ/rVL9SIvOp+7EG/llxjw3LYsklAiLjCFkxFGW11f05UJkZD/RLRSz0JH/CAchF DwWVrLIEDrZbCEMfM2uoRIRfmb9Je536I9PWA= Received: by 10.112.23.65 with SMTP id k1mr2208034lbf.77.1328299739281; Fri, 03 Feb 2012 12:08:59 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.96.40 with HTTP; Fri, 3 Feb 2012 12:08:39 -0800 (PST) In-Reply-To: <1327548042270-7225877.post@n2.nabble.com> References: <1327548042270-7225877.post@n2.nabble.com> From: Kevin Sutter Date: Fri, 3 Feb 2012 14:08:39 -0600 Message-ID: Subject: Re: To TransactionAttributeType.NOT_SUPPORTED or not to TransactionAttributeType.NOT_SUPPORTED To: users@openjpa.apache.org Content-Type: multipart/alternative; boundary=90e6ba3090f21d7baa04b814e2dd X-Virus-Checked: Checked by ClamAV on apache.org --90e6ba3090f21d7baa04b814e2dd Content-Type: text/plain; charset=ISO-8859-1 Hi Tom, Sorry that I missed this one... Maybe you have already figured out the answer... First off, JPA does not play into your transaction timeout or suspension processing. All of that is part of the WebSphere application server processing, so I would reference the InfoCenter for more definitive answers [1]. But, I do know that any active transaction will be suspended when a NOT_SUPPORTED method is encountered. So, any time that your innerMethod is invoked, the current transaction would be suspended. As far as whether the timer keeps running, I would guess "yes", but I think you need some JTA experts to be sure. HTH, Kevin [1] http://publib.boulder.ibm.com/infocenter/wasinfo/v8r0/topic/com.ibm.websphere.express.iseries.doc/info/iseriesexp/ae/tjta_settlog.html On Wed, Jan 25, 2012 at 9:20 PM, Tom Rowe < charles.paisley.the.baby.crusher@gmail.com> wrote: > Greetings to my former JPA friends. I have a few questions about > TransactionAttributeType.NOT_SUPPORTED. > My environment is WAS v7, but I think it matters not. > Here's the setup.. > > - - - - - - - - - - - - - - - - - - - - - - > > @Stateless > public class OuterService implements IOuterService { > > @PersistenceContext( unitName = "OuterService" ) > EntityManager em; > > @EJB( name = "ejblocal:com.mycompany.mypackage.IInnerService" ) > IInnerService innerService; > > .... > > public Object outerMethod() throws Exception { > ... > innerService.innerMethod(); > ... > } > } > > - - - - - - - - - - - - - - - - - - - - - - > > package com.mycompany.mypackage; > @Stateless > public class InnerService implements IInnerService { > > @PersistenceContext( unitName = "OuterService" ) > EntityManager em; // PC matches! > > .... > > @TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED) > public Object innerMethod() throws Exception { > ... > } > } > > - - - - - - - - - - - - - - - - - - - - - - > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/persistence > http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd" > version="2.0"> > > MY-JTA-DATA-SOURCE > ... > ... > > value="me" /> > value="password" /> > value="validate" /> > > > > > - - - - - - - - - - - - - - - - - - - - - - > > Questions: > 1. Do WebSphere transaction timeouts (default=120 secs) get suspended > across > calls to innerMethod() because of TransactionAttributeType.NOT_SUPPORTED? > 2. Do WebSphere transaction timeouts get suspended across calls to > outerMethod() when/if innerService.innerMethod() is invoked? > > Thanks, in advance for your time and consideration.. > > Tom Rowe > > -- > View this message in context: > http://openjpa.208410.n2.nabble.com/To-TransactionAttributeType-NOT-SUPPORTED-or-not-to-TransactionAttributeType-NOT-SUPPORTED-tp7225877p7225877.html > Sent from the OpenJPA Users mailing list archive at Nabble.com. > --90e6ba3090f21d7baa04b814e2dd--