-
1. Re: Transaction timeout (Phorum)
marklittle Mar 14, 2006 8:01 AM (in response to marklittle)Author: Mark Little
Date: 10-01-04 19:49
> I'm trying to test a transaction timing out.
>
> I changed the following in jboss-service.xml file:
>
> code="com.arjuna.ats.jbossatx.jts.TransactionManagerService"
> name="jboss:service=TransactionManager"
>
> xmbean-dd="resource:xmdesc/TransactionManagerService-xmbean.xml">
> 300
> true
> name="RunInVMRecoveryManager">true
>
>
>
> I changed the 300 to 3. When I started JBoss, it confirmed
> that the transaction timeout was 3:
>
> 07:28:21,027 INFO [TransactionManagerService] Transaction
> timeout set to 3
>
>
> I then ran both one phase and two phase commit transactions
> with a sleep in our code so the transaction takes from 5 to 15
> seconds to complete.
>
> All transactions completed successfully, without any errors
> or rollbacks.
>
> Am I doing something wrong? Is there a different timeout
> value I should be configuring?
Hi. You say that the transaction takes from 5 to 15 seconds to complete because of a sleep. Where does the sleep occur? Is it before the transaction begins to commit or during the two-phase commit protocol?
Mark. -
2. Re: Transaction timeout (Phorum)
marklittle Mar 14, 2006 8:01 AM (in response to marklittle)Author: burdeasa2
Date: 10-04-04 14:04
The sleep is after the XAResource.start has been called and returned, but before XAResource.prepare has been called. -
3. Re: Transaction timeout (Phorum)
marklittle Mar 14, 2006 8:02 AM (in response to marklittle)Author: Mark Little
Date: 10-04-04 14:22
burdeasa2 wrote:
> The sleep is after the XAResource.start has been called and
> returned, but before XAResource.prepare has been called.
Hi. There may be an issue with our JBoss service and that property, which we're looking into now. However, if you want to check transaction timeouts and other, ATS specific functionality, you can always modify the arjunajts-properties.xml in server/all/conf
Set the following properties:
com.arjuna.ats.arjuna.coordinator.txReaperMode=DYNAMIC
and
com.arjuna.ats.arjuna.coordinator.txReaperTimeout=your value in milliseconds
I'll let you know what we discover with regard to the other route for setting the timeout.
Mark.