Thanks for the link.
Seems like the reaperTimeout is the sleep time for the reaper itself.
com.arjuna.ats.arjuna.coordinator.defaultTimeout seems to be the maximum time a
transaction can take before getting rolled back by the reaper.
I tried setting the defaultTimeout but didn't see like it worked.
In the deploy folder there is a file called transaction-jboss-beans.xml in this
file I have set transactionTimeout that did the trick.
| <bean name="TransactionManager"
class="com.arjuna.ats.jbossatx.jta.TransactionManagerService">
|
<annotation>@org.jboss.aop.microcontainer.aspects.jmx.JMX(name="jboss:service=TransactionManager",
exposedInterface=com.arjuna.ats.jbossatx.jta.TransactionManagerServiceMBean.class,
registerDirectly=true)</annotation>
|
| <property name="transactionTimeout">1800</property>
| <property
name="objectStoreDir">${jboss.server.data.dir}/tx-object-store</property>
| <property name="mbeanServer"><inject bean="JMXKernel"
property="mbeanServer"/></property>
|
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4225762#4225762
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4225762
_______________________________________________
jboss-user mailing list
jboss-user@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-user
