Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

JBoss transaction timeout setting?

We have a timer service triggered task in JBoss 5.1.0.GA application and the problem is that we cannot change the transaction time out. This long Lucene indexing can take longer than the default 300 second limit.

The question is how to change the timeout value, adding @TransactionTimeout(1800) to the worker method or the class did not have any effect.

Edit: Setting this in deploy/transaction-jboss-beans.xml works fine:

<property name="transactionTimeout">1800</property>

but the annotation doesn't seem to have effect on either timer initiated or normal stateless EJBs.

like image 826
Petteri H Avatar asked Feb 02 '10 14:02

Petteri H


People also ask

What is JBoss transaction timeout?

The default JBoss transaction timeout is 300 seconds. This may be too short for your site's purposes, particularly if you have a large ATG Commerce catalog. To increase the transaction timeout: Go to the <JBossDir>/server/atg/conf/jboss-service. xml file.

How do I increase my JTA timeout?

It is recommended that you set the 1Transact timeout value to be at least 600 seconds (10 minutes.) To change this setting, connect to WebLogic Server Administration Console. On the Domain > Configuration > JTA >Timeout Seconds tab, modify the Java Transaction API (JTA) timeout to be a minimum of 600.

How do I increase connection timeout in WildFly?

Transaction timeout in WildFly / JBoss can be configured in the transactions subsystem or at EJB level. When the transaction is configured in the transactions subsystem it will be the default transaction timeout for all JTA transactions. When configured at EJB level, the timeout will be specific of that EJB.


1 Answers

Transaction timeout,default settings in JBOSS EPA 7.1 version is 300.

jboss portal screen

Add this line(<coordinator-environment enable-tsm-status="true" default-timeout="1200"/>) add the configuration file in path "..standalone/configuration/standalone.xml"

                                    ....
<subsystem xmlns="urn:jboss:domain:transactions:4.0">
            <core-environment>
                <process-id>
                    <uuid/>
                </process-id>
            </core-environment>
            <recovery-environment socket-binding="txn-recovery-environment" status-socket-binding="txn-status-manager"/>
            <coordinator-environment enable-tsm-status="true" default-timeout="1200"/>
            <object-store path="tx-object-store" relative-to="jboss.server.data.dir"/>
 </subsystem>
like image 123
fgul Avatar answered Oct 16 '22 06:10

fgul