Return-Path: X-Original-To: apmail-aries-user-archive@www.apache.org Delivered-To: apmail-aries-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0D1E2B2BB for ; Thu, 12 Jan 2012 18:09:43 +0000 (UTC) Received: (qmail 75009 invoked by uid 500); 12 Jan 2012 18:09:42 -0000 Delivered-To: apmail-aries-user-archive@aries.apache.org Received: (qmail 74930 invoked by uid 500); 12 Jan 2012 18:09:41 -0000 Mailing-List: contact user-help@aries.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@aries.apache.org Delivered-To: mailing list user@aries.apache.org Received: (qmail 74922 invoked by uid 99); 12 Jan 2012 18:09:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Jan 2012 18:09:41 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of bengt.rodehav@gmail.com designates 209.85.214.178 as permitted sender) Received: from [209.85.214.178] (HELO mail-tul01m020-f178.google.com) (209.85.214.178) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Jan 2012 18:09:34 +0000 Received: by obbtb2 with SMTP id tb2so1313304obb.23 for ; Thu, 12 Jan 2012 10:09:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=Ad9pwEaClssc1pzDxESsXHx6dHoQweKb+gwrEIlPlp8=; b=rAP7FFE/di2GFPVgYwQPq4D3Gw4BixNDs76zeq0npKwaakocxA4XzX8RuR+gnZk0QR odDqCPobsrdHwbvY9In8J9Z1+jwG2LOnKq/WLgKieqnL4QT+rGiX0O+bMuOvZB+ViGp7 CYhsF7pMOjZnzWALNPHpU9iu4s4ZJD2vYKdOE= MIME-Version: 1.0 Received: by 10.50.217.168 with SMTP id oz8mr1162677igc.24.1326391753156; Thu, 12 Jan 2012 10:09:13 -0800 (PST) Sender: bengt.rodehav@gmail.com Received: by 10.182.152.69 with HTTP; Thu, 12 Jan 2012 10:09:13 -0800 (PST) In-Reply-To: <99E69502-E64E-4090-8155-5464E1921A03@yahoo.com> References: <000363B9-FC1C-4866-8472-A10E547AC20E@yahoo.com> <99E69502-E64E-4090-8155-5464E1921A03@yahoo.com> Date: Thu, 12 Jan 2012 19:09:13 +0100 X-Google-Sender-Auth: ipys7PEofU1xDKuzR30sF3dc1CQ Message-ID: Subject: Re: How to configure transaction timeout? From: Bengt Rodehav To: "user@aries.apache.org" Content-Type: multipart/alternative; boundary=14dae934053747a7e704b658a563 X-Virus-Checked: Checked by ClamAV on apache.org --14dae934053747a7e704b658a563 Content-Type: text/plain; charset=ISO-8859-1 David, I have verified that the configuration is applied to the transaction service I just can't see that it has any effect. I guess I can start debugging but I was hoping to avoid that. Do you know if there are any integration tests that tests the transaction timeout? /Bengt Den torsdagen den 12:e januari 2012 skrev David Jencks< david_jencks@yahoo.com>: > I would guess that perhaps your configuration is not actually getting supplied to the managed service? If you are running in karaf you can use confiig:list to make sure config admin is aware of your config. You might also want to debug the aries code and make sure that the configuration is actually getting supplied to the service. > david jencks > On Jan 12, 2012, at 6:36 AM, Bengt Rodehav wrote: > > Hello again Alasdair, > I finally got around to test configuration of Aries Transaction. I created the following configuration (using PID org.apache.aries.transaction): > aries.transaction.timeout=1 > aries.transaction.howl.logFileDir=${karaf.data}/txlog/ > I set the logfile directory as well as the transaction timeout (I peeked at how they do it in Servicemix). I set the timeout to a low value in order to test that I actually get a transaction timeout. I also perform a 5s sleep in a transacted method to force a transaction timeout. > But, I never get a transaction timeout and I never get a transaction log file in the "logFileDir" directory. I'm not beginning to fear that my methods are not transacted. How can I verify this? > Under what circumstances would a transaction log file be created? I assumed that it would be created when the first transaction was created. Or, do I also need to add the following line? > aries.transaction.recoverable=true > I've tried that but still no logfile was created. > I also noticed that the default value for "aries.transaction.howl.maxBuffers" is 0 while the default value for "aries.transaction.howl.minBuffers" is 4. Is that correct? At first sight I would think it should be the other way around. > /Bengt > > > > > > > 2011/12/29 Bengt Rodehav > > Thanks Alasdair - will look into it. > /Bengt > > 2011/12/28 Alasdair Nottingham > > Hi, > The pid for configuring transactions is "org.apache.aries.transaction". > Alasdair > > On 14 December 2011 14:33, Bengt Rodehav wrote: > > It turned out that my error was not due to the transaction timing out but to violation of unique constraints. Nevertheless, I would like to know how to control the transaction timeout in Aries transaction. > /Bengt > > 2011/12/14 Bengt Rodehav > > Thanks for your reply David, > I'll see if I can figure out the pid although this seems like something that really needs to be documented in Aries. If the default timeout is 600 seconds then this is probably not the reason of the errors I see. I need a time out of about 30 s which then is much less than the default. > I have been using MySql but I'm in the process of switching to SQL Server 2005. MySql worked fine but I started having problems committing the longer transactions with SQL Server 2005 which caused me to suspect a transaction timeout. Perhaps the timeout is not propagated to SQL Server like you hinted. > /Bengt > > 2011/12/14 David Jencks > > Transaction is set up as a managed service factory. I haven't figured out exactly how this results in a tm instance without any visible configuration. > If you can figure out what is triggering the creation of a tm and the pid, the property to set is called aries.transaction.timeout and the default value is 600 (seconds) or 10 minutes. --14dae934053747a7e704b658a563 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
David,

I have verified that the configuration is applied to the = transaction service I just can't see that it has any effect. I guess I = can start debugging but I was hoping to avoid that. Do you know if there ar= e any integration tests that tests the transaction timeout?

/Bengt


Den torsdagen den 12:e januari 2012 skrev David Jenck= s<david_jencks@yahoo.com&g= t;:
> I would guess that perhaps your configuration is not actually g= etting supplied to the managed service? =A0If you are running in karaf you = can use confiig:list to make sure config admin is aware of your config. =A0= You might also want to debug the aries code and make sure that =A0the confi= guration is actually getting supplied to the service.
> david jencks
> On Jan 12, 2012, at 6:36 AM, Bengt Rodehav wrote:=
>
> Hello again Alasdair,
> I finally got around to test= configuration of Aries Transaction. I created the following configuration = (using PID=A0org.apache.aries.transaction):
> aries.transaction.timeout=3D1
> aries.transaction.howl.logFileDi= r=3D${karaf.data}/txlog/
> I set the logfile directory as well as the= transaction timeout (I peeked at how they do it in Servicemix). I set the = timeout to a low value in order to test that I actually get a transaction t= imeout. I also perform a 5s sleep in a transacted method to force a transac= tion timeout.
> But, I never get a transaction timeout and I never get a transaction l= og file in the "logFileDir" directory. I'm not beginning to f= ear that my methods are not transacted. How can I verify this?
> Unde= r what circumstances would a transaction log file be created? I assumed tha= t it would be created when the first transaction was created. Or, do I also= need to add the following line?
> aries.transaction.recoverable=3Dtrue
> I've tried that but s= till no logfile was created.
> I also noticed that the default value = for "aries.transaction.howl.maxBuffers" is 0 while the default va= lue for "aries.transaction.howl.minBuffers" is 4. Is that correct= ? At first sight I would think it should be the other way around.
> /Bengt
>
>
>
>
>
>
> 2011/12= /29 Bengt Rodehav <bengt@rodehav.co= m>
>
> Thanks Alasdair - will look into it.
> /Ben= gt
>
> 2011/12/28 Alasdair Nottingham <not@apache.org>
>
> Hi,
> The pid for confi= guring transactions is "org.apache.aries.transaction".
> Al= asdair
>
> On 14 December 2011 14:33, Bengt Rodehav <bengt@rodehav.com> wrote:
>
> It tur= ned out that my error was not due to the transaction timing out but to viol= ation of unique constraints. Nevertheless, I would like to know how to cont= rol the transaction timeout in Aries transaction.
> /Bengt
>
> 2011/12/14 Bengt Rodehav <bengt@rodehav.com>
>
> Thanks for you= r reply David,
> I'll see if I can figure out the pid although th= is seems like something that really needs to be documented in Aries. If the= default timeout is 600 seconds then this is probably not the reason of the= errors I see. I need a time out of about 30 s which then is much less than= the default.
> I have been using MySql but I'm in the process of switching to SQL= Server 2005. MySql worked fine but I started having problems committing th= e longer transactions with SQL Server 2005 which caused me to suspect a tra= nsaction timeout. Perhaps the timeout is not propagated to SQL Server like = you hinted.
> /Bengt
>
> 2011/12/14 David Jencks <david_jencks@yahoo.com>
>
> Trans= action is set up as a managed service factory. =A0I haven't figured out= exactly how this results in a tm instance without any visible configuratio= n.
> If you can figure out what is triggering the creation of a tm and the = pid, the property to set is called=A0aries.transaction.timeout and the defa= ult value is 600 (seconds) or 10 minutes. --14dae934053747a7e704b658a563--